22 Nov
2004
22 Nov
'04
9:11 p.m.
I increased the installed ram in this box to 40MB (all I had -- it maxes
out at 64MB anyway) with no change in the behavior; I tried running
with '-m 2, -m 4 -m 6 -m 8 and default (-m 32)' -- with '-m 2' two
processes start and there is no core dump but 'serctl ps' will kill
one of them and the other one hangs (in a loop accessing something in
the filesystem -- haven't traced it yet). This is with 'fork=no' in
ser.cfg. Only with 'fork=yes' will ser start (only one process) and
run stable. Regardless of the fork setting, ser will not remain in
the foreground.
Without using command-line options:
"fork=yes" set in ser.cfg results in only a single process running in
the background;
"fork=no" set in ser'cfg results in several processes starting followed
by a segfault (in one of them, the rest remain running):
(gdb) bt
#0 0x83a2584 in _atomic_lock ()
#1 0x83a2564 in _spinlock_debug ()
also, the fifo is created and 'serctl ps' will list the (2)
running processes, but this query will kill those
processes.
Michael