18 Feb
2003
18 Feb
'03
10:40 a.m.
Hi Nils!
Le mar 18/02/2003 à 16:03, Nils Ohlmeier a écrit :
I know about it but...
On Tuesday 18 February 2003 15:57, Sebastien Pierre
wrote:
I thought I did not install syslog with root privileges, so I did not
look in the *obvious* file!
Anyway, I put a "log_sterror=yes" line at the beginning of my SER
configuration script, but SER keeps outputting on /var/log/messages and
not on STDERR... what did I do wrong ?
I was just wondering (did not find in User or Dev
guide) where to get
the result of SER "log" action... I have written a fake SIP UA that
syslog (probably /var/log/messages) if log_stderror=no, otherwise stderr (your
console). sends SIP
messages written in a file to test custom SER configurations,
but I don't know if SER properly receives my messages or executes my
routing program. Any advices ?
Congratulation for reinventing the wheel ->
http://sipsak.berlios.de :-) > sipsak -s sip:alice@localhost
error: this
FQDN or IP is not valid: frwed00304
I'm still puzzled about this FQDN and my hostname... and I could not
resist making a 20 lines Python script to get SER tested ;)
-- Seb
18 Feb
18 Feb
10:56 a.m.
Hi Sebastien,
On Tuesday 18 February 2003 16:40, Sebastien Pierre wrote:
I see.
Because this is a common problem i will probably introduce a new option to
sipsak.
Regards
Nils Ohlmeier
Le mar 18/02/2003 à 16:03, Nils Ohlmeier a écrit :
Hard to say without seeing the config file. But '-E' as command line parameter
should work and will overwrite any value in your config file.
syslog (probably /var/log/messages) if
log_stderror=no, otherwise stderr
(your console).
I thought I did not install syslog with root privileges, so I did not
look in the *obvious* file!
Anyway, I put a "log_sterror=yes" line at the beginning of my SER
configuration script, but SER keeps outputting on /var/log/messages and
not on STDERR... what did I do wrong ? Congratulation
for reinventing the wheel -> http://sipsak.berlios.de :-)
I know about it but...
> sipsak -s sip:alice@localhost
error: this FQDN or IP is not valid: frwed00304
I'm still puzzled about this FQDN and my hostname... and I could not
resist making a 20 lines Python script to get SER tested ;) 
12:18 p.m.
On Feb 18, 2003 at 16:56, Nils Ohlmeier <nils(a)ohlmeier.de> wrote:
Content-Description: signed data
Hi Sebastien,
On Tuesday 18 February 2003 16:40, Sebastien Pierre wrote:
No, the options in the config file take precedence over the command
line. So if logstderror=no is in the config file you cannot override it
from the command line. I know it should be the other way arround (this
thing is on my TODO list for a long time).
Andrei
Le mar 18/02/2003 ?? 16:03, Nils Ohlmeier a
??crit :
Hard to say without seeing the config file. But '-E' as command line parameter
should work and will overwrite any value in your config file. syslog (probably /var/log/messages) if
log_stderror=no, otherwise stderr
(your console).
I thought I did not install syslog with root privileges, so I did not
look in the *obvious* file!
Anyway, I put a "log_sterror=yes" line at the beginning of my SER
configuration script, but SER keeps outputting on /var/log/messages and
not on STDERR... what did I do wrong ? 
11:39 a.m.
At 04:40 PM 2/18/2003, Sebastien Pierre wrote:
> syslog (probably /var/log/messages) if
log_stderror=no, otherwise stderr (your
[...]
Anyway, I put a "log_sterror=yes" line at the
beginning of my SER
configuration script, but SER keeps outputting on /var/log/messages and
not on STDERR... what did I do wrong ?
s/log_sterror/log_stderror
-jiri
12:13 p.m.
On Feb 18, 2003 at 16:40, Sebastien Pierre <sebastien.pierre(a)sxb.bsf.alcatel.fr>
wrote:
Hi Nils!
Le mar 18/02/2003 ?? 16:03, Nils Ohlmeier a ??crit :
Maybe you have another line with log_stderror=no somewhere else in the
config file.
Andrei
On Tuesday 18 February 2003 15:57, Sebastien
Pierre wrote:
I thought I did not install syslog with root privileges, so I did not
look in the *obvious* file!
Anyway, I put a "log_sterror=yes" line at the beginning of my SER
configuration script, but SER keeps outputting on /var/log/messages and
not on STDERR... what did I do wrong ?
I was just wondering (did not find in User or Dev
guide) where to get
the result of SER "log" action... I have written a fake SIP UA that
syslog (probably /var/log/messages) if log_stderror=no, otherwise stderr (your
console).
7768
days inactive
7768
days old
4 comments
4 participants
participants (4)
-
Andrei Pelinescu-Onciul -
Nils Ohlmeier -
Sebastien Pierre -
serhelp (Jiri)