22 Jun
2005
22 Jun
'05
4:59 p.m.
fork=no mode is for debugging only, SER running in non-forking mode has
several limitations (such as it can listen only on one interface).
I would recommend you to use fork=yes and monitor syslog for ser
messages.
Jan.
On 22-06-2005 17:26, Chia Huey Lim wrote:
Hi. I am using ser 0.9.0.
The moment I change from fork = yes to fork = no to enter debug mode
And I attempt to "serctl restart"
I was stuck in
[root@localhost ser-0.9.0]# serctl start
Starting SER :
The moment I change back to fork = yes, I can start SER again.
Any further adjustment I need to do when I switch from fork = yes to fork =
no?
Thanks in advance.
Regards,
Chia
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers