[rsyslog-notify] Forum Thread: Re: ruleset does not work, no writing into file - (Mode 'reply')

[noreply at adiscon.com]

User: vogster 
Forumlink: http://kb.monitorware.com/viewtopic.php?p=24396#p24396

Message: 
----------
Hello everybody,

sorry for the delay but I needed more time so work myself into the rsyslog
system.
The problems I wrote about are fixed, thank you for the tip with the debug
option –d –n, this help a lot. Sadly I cannot be able to relate the problem
in detail, maybe on my self-written client.
But I have still one problem with the startup of rsyslog (I use version
5.8.10, standard on CentOS 6.3 x64). After I started rsyslog (manually via
service rsyslog start or automatically with system startup) the service
does nothing. In my configuration a listener for UDP Ports 50001 to 50003
waits for messages. 
When I stop the service via service rsyslog stop and restart it with simple
rsyslogd (with –d –n or without) it runs perfect and does anything I
configured.
In the documentation on rsyslog.com I read about the $PrivDropToUser option
an I implemented it with $PrivDropToUser root in my .conf file but there
was no effect.
Does anybody have an idea what the problem is?

Vogster