Hi everybody,
I got a problem with launching ser. It launch correctly, but quit immediately without prompting an error message. I took a look in the /var/log/messages file and there is what I found:
ser: INFO: SIGCHLD received: we do not worry about grand-children ser: DEBUG: tm_shutdown: releasing timers ser: DEBUG: tm_shutdown : removing semaphores ser: DEBUG: tm_shutdown : done ser: shm_mem_destroy ser: destroying the shared memory lock
This computer is running SuSE 9.1 with ser 0.8.12 and this problem wasn't there last week. It just appeared today. Since I'm not the only one working on this computer, something could have been modified, but I'm wondering what...
Cyprien
On Jul 12, 2004 at 12:54, Cyprien Simons cyprien.simons@tu-berlin.de wrote:
Hi everybody,
I got a problem with launching ser. It launch correctly, but quit immediately without prompting an error message. I took a look in the /var/log/messages file and there is what I found:
ser: INFO: SIGCHLD received: we do not worry about grand-children ser: DEBUG: tm_shutdown: releasing timers ser: DEBUG: tm_shutdown : removing semaphores ser: DEBUG: tm_shutdown : done ser: shm_mem_destroy ser: destroying the shared memory lock
Try a config check (ser -c -f /etc/ser/ser.cfg). If it's ok enable coredumps: ulimit -c unlimited ser -w /tmp/ #......
and see if you get a core in temp. Also send us the full start log.
Andrei
it's ok. I found what it was. The fifo file hadn't the correct permissions...
On Wednesday 14 July 2004 15:01, Andrei Pelinescu-Onciul wrote:
On Jul 12, 2004 at 12:54, Cyprien Simons cyprien.simons@tu-berlin.de
wrote:
Hi everybody,
I got a problem with launching ser. It launch correctly, but quit immediately without prompting an error message. I took a look in the /var/log/messages file and there is what I found:
ser: INFO: SIGCHLD received: we do not worry about grand-children ser: DEBUG: tm_shutdown: releasing timers ser: DEBUG: tm_shutdown : removing semaphores ser: DEBUG: tm_shutdown : done ser: shm_mem_destroy ser: destroying the shared memory lock
Try a config check (ser -c -f /etc/ser/ser.cfg). If it's ok enable coredumps: ulimit -c unlimited ser -w /tmp/ #......
and see if you get a core in temp. Also send us the full start log.
Andrei
-
Andrei Pelinescu-Onciul -
Cyprien Simons