2012/12/21 Radu Gheorghe <[email protected]>: > Thanks Rainer! It actually works like that, if you comment out "expect > fork" from /etc/init/rsyslog.conf
Just wanted to mention that removing the forking has an unpleasant side-effect: Forking in daemons is usually a way to signal that it has setup its communication channels (sockets to read from etc). Upstart would only fire the "rsyslog started" event once that fork happened. Now, removing forking from the upstart job file means, upstart fires "rsyslog started" as soon as the binary has been spawned but this doesn't necessarily mean it is ready yet to listen on /dev/log. Subsequent daemons relying on syslog are possibly started too early and there is a chance that you lose syslog messages as the startup sequence has become racy. So removing the forking from the upstart job file has some consequences you need to be aware of. (fwiw, systemd solves that problem rather nicely). Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
