The following happens on my Arch Linux system.
When I start the apl binary (without Emacs) I'm getting a "connection
refused" error. The log with *-l 37* is reproduced below.
The APserver is properly started (I can see it in the process listing), but
after I call )OFF, it doesn't get killed.
Note that if I start APserver separately, I do not get any errors, and
everything seems to work correctly.
Here's the output from -l 37 (errors highlighted in red):
$ *dist/bin/apl -l 37 --silent*
sizeof(Svar_record) is 328
sizeof(Svar_partner) is 28
initializing paths from argv[0] = dist/bin/apl
initializing paths from $PWD = /home/emartenson/src/apl
APL_bin_path is: ./dist/bin
APL_bin_name is: apl
Reading config file /home/emartenson/src/apl/dist/etc/gnu-apl.d/preferences
...
config file /home/emartenson/.config/gnu-apl/preferences is not
present/readable
0 input files:
Using TCP socket towards APserver...
connecting to 127.0.0.1 TCP port 16366
(this is expected to fail, unless APserver was started manually)
forking new APserver listening on 127.0.0.1 TCP port 16366
connecting to 127.0.0.1 TCP port 16366
(this is supposed to succeed.)
::connect() to existing APserver failed: Connection refused
PID is 24054
argc: 4
argv[0]: 'dist/bin/apl'
argv[1]: '-l'
argv[2]: '37'
argv[3]: '--silent'
uprefs.user_do_svars: 1
uprefs.system_do_svars: 1
uprefs.requested_id: 0
uprefs.requested_par: 0
Svar_DB not connected in Svar_DB::is_registered_id()
id.proc: 1001 at ProcessorID.cc:77
Processor ID was completely initialized: 1001:0:0
system_do_svars is: 1
* ⎕SVQ⍳0*
Svar_DB not connected in Svar_DB::get_offering_processors()
100 210
Regards.
Elias
