Hi,
I am using the latest cvs code (although the follwoing occurs since a few days) -- I first thought it is some file "under development" and that is why I have updated from CVS frequently, but I am not convinced of this anymore, as you are usually good in fixing things up quickly. Maybe you could interpret this for me? (the lines referring to polserver connector are our own module, but that seems to be fine here). many thanks,
Stephan
------------ LOG below. ------------
Apr 2 10:54:22 d254196 ser: Listening on Apr 2 10:54:22 d254196 ser: 127.0.0.1 [127.0.0.1]::5060 Apr 2 10:54:22 d254196 ser: 139.153.254.196 [139.153.254.196]::5060Apr 2 10:54:22 d254196 ser: Aliases: localhost:5060 localhost.localdomain:5060 d254196.cs.stir.ac.uk:*Apr 2 10:54:22 d254196 ser: ser startup succeeded Apr 2 10:54:22 d254196 ser: INFO: signal 13 received Apr 2 10:54:22 d254196 ser: INFO: signal 13 received Apr 2 10:54:22 d254196 /usr/local/sbin/ser[8739]: mod_init(): Database connection opened successfulyApr 2 10:54:22 d254196 /usr/local/sbin/ser[8739]: pol server connector - initializingApr 2 10:54:22 d254196 /usr/local/sbin/ser[8739]: pol server connector - initializing: doneApr 2 10:54:22 d254196 /usr/local/sbin/ser[8739]: INFO: udp_init: SO_RCVBUF is initially 65535Apr 2 10:54:22 d254196 /usr/local/sbin/ser[8739]: INFO: udp_init: SO_RCVBUF is finally 131070Apr 2 10:54:22 d254196 /usr/local/sbin/ser[8739]: INFO: udp_init: SO_RCVBUF is initially 65535Apr 2 10:54:22 d254196 /usr/local/sbin/ser[8739]: INFO: udp_init: SO_RCVBUF is finally 131070Apr 2 10:54:22 d254196 /usr/local/sbin/ser[8752]: INFO: fifo process starting: 8752Apr 2 10:54:22 d254196 /usr/local/sbin/ser[8752]: SER: open_uac_fifo: fifo server up at /tmp/ser_fifo...Apr 2 10:54:22 d254196 /usr/local/sbin/ser[8739]: INFO: SIGCHLD received: we do not worry about grand-childrenApr 2 10:54:22 d254196 /usr/local/sbin/ser[8764]: BUG: tcp_main_loop: dead child 11Apr 2 10:54:22 d254196 /usr/local/sbin/ser[8764]: BUG: tcp_main_loop: dead child 12Apr 2 10:54:22 d254196 /usr/local/sbin/ser[8764]: BUG: tcp_main_loop: dead child 13Apr 2 10:54:22 d254196 /usr/local/sbin/ser[8764]: BUG: tcp_main_loop: dead child 14Apr 2 10:54:22 d254196 /usr/local/sbin/ser[8739]: child process 8763 exited by a signal 11Apr 2 10:54:22 d254196 /usr/local/sbin/ser[8739]: core was not generated Apr 2 10:54:22 d254196 /usr/local/sbin/ser[8739]: child process 8762 exited by a signal 11Apr 2 10:54:22 d254196 /usr/local/sbin/ser[8739]: core was not generated Apr 2 10:54:22 d254196 /usr/local/sbin/ser[8739]: child process 8761 exited by a signal 11Apr 2 10:54:22 d254196 /usr/local/sbin/ser[8739]: core was not generated Apr 2 10:54:22 d254196 /usr/local/sbin/ser[8739]: child process 8760 exited by a signal 11Apr 2 10:54:22 d254196 /usr/local/sbin/ser[8739]: core was not generated Apr 2 10:54:22 d254196 /usr/local/sbin/ser[8739]: INFO: terminating due to SIGCHLDApr 2 10:54:23 d254196 /usr/local/sbin/ser[8741]: INFO: signal 15 received Apr 2 10:54:23 d254196 /usr/local/sbin/ser[8742]: INFO: signal 15 received Apr 2 10:54:23 d254196 /usr/local/sbin/ser[8743]: INFO: signal 15 received Apr 2 10:54:23 d254196 /usr/local/sbin/ser[8744]: INFO: signal 15 received Apr 2 10:54:23 d254196 /usr/local/sbin/ser[8745]: INFO: signal 15 received Apr 2 10:54:23 d254196 /usr/local/sbin/ser[8746]: INFO: signal 15 received Apr 2 10:54:23 d254196 /usr/local/sbin/ser[8750]: INFO: signal 15 received Apr 2 10:54:23 d254196 /usr/local/sbin/ser[8751]: INFO: signal 15 received Apr 2 10:54:23 d254196 /usr/local/sbin/ser[8759]: INFO: signal 15 received Apr 2 10:54:23 d254196 /usr/local/sbin/ser[8764]: INFO: signal 15 received Apr 2 10:54:23 d254196 /usr/local/sbin/ser[8752]: INFO: signal 15 received