12 Jan
2007
12 Jan
'07
11:01 a.m.
I founded out that ser can utilize the local* subsystem so I used It but still those are
only the debuging messages like:
Jan 12 10:56:07 tomix ser: init_tcp: using epoll_lt as the io watch method (auto
detected)
Jan 12 10:56:07 tomix ./ser[4671]: Maxfwd module- initializing
Jan 12 10:56:07 tomix ./ser[4671]: INFO: xlog null is "<null>"
Jan 12 10:56:07 tomix ./ser[4671]: INFO: udp_init: SO_RCVBUF is initially 109568
an the others like:
Listening on
udp: 127.0.0.1 [127.0.0.1]:5060
udp: 192.168.1.2 [192.168.1.2]:5060
tcp: 127.0.0.1 [127.0.0.1]:5060
tcp: 192.168.1.2 [192.168.1.2]:5060
Aliases:
tcp: tomix:5060
tcp: localhost:5060
udp: tomix:5060
udp: localhost:5060
are still send to terminal, is there a way in the ser.cfg file to redirect them as well to
syslog? like with the log_stderr option??
#tomasz
HI, see inline.
* TZieleniewski <tzieleniewski(a)o2.pl> [070111 23:37]:
Greger V. Teigre napisa?(a):
What about /usr/local/sbin/ser -ddddddddddddddddddd -E 1>/myfile.txt 2>/myfile.txt
- Atle
>
> Tomasz
> _______________________________________________
> Serusers mailing list
> Serusers(a)lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers Well, you can define a new log file for another
facility in your /etc/syslog.conf and then configure ser to log to that
facility instead. Better than using stderr
g-)
TZieleniewski wrote:
Well I know how to define the new log in syslog.conf but how can I distinguish
that it is only ser??
i mean how can i point that particular subsystem is ser?? and how to set it in ser to
log to such output file?? Hi !
Is there in ser 0.10.99 a way to send the output to the file instead of syslog??
Previously for ser 0.9.7 I had it done throught the serctl tool. I had the
logstderror=yes
in my ser.cfg and the output was redirected to log file pointed by SER_LOGFILE inside
serctl.
Tomasz
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers