http://bugzilla.novell.com/show_bug.cgi?id=606972 http://bugzilla.novell.com/show_bug.cgi?id=606972#c1 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |mt@novell.com, | |tambet@novell.com Resolution| |WONTFIX --- Comment #1 from Dr. Werner Fink 2010-05-20 07:25:51 UTC --- It is invalid as both syslogd and syslog-ng clearly depends on network (e.g. NetworkManager) otherwise logging over network will not work which is a major feature. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=606972 http://bugzilla.novell.com/show_bug.cgi?id=606972#c3 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |marc@marcchamberlin.com Target Milestone|--- |Future 11.3 Severity|Normal |Enhancement --- Comment #3 from Dr. Werner Fink 2010-05-21 07:40:14 UTC --- In which way do you want break syslog-ng *and* syslogd *and* rsyslogd into two parts? The only possiblity would exist only and only if all three syslogging daemons would support not to hang on a not existing network interface including the possiblity to to (re)open the network after e.g. a SIGHUP. The other way of rewriting the configuration on the fly between a restart is (IMHO) a nogo. AFAIK from the old syslogd it does not support this. If the other two daemons do support this I don't know. Maybe Marius can say a few words. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=606972 http://bugzilla.novell.com/show_bug.cgi?id=606972#c5 --- Comment #5 from Marius Tomaschewski 2010-05-26 10:37:20 UTC --- Please attach also the /etc/init.d/.depend.start file. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=606972 http://bugzilla.novell.com/show_bug.cgi?id=606972#c7 --- Comment #7 from Marc Chamberlin 2010-05-26 18:14:27 UTC --- (In reply to comment #4)

Marc,

the syslog service is already splitted -- there are two scripts:

- /etc/init.d/earlysyslog, that is responsible to log the early startup messages and - /etc/init.d/syslog, that takes over when the network is up

Does it not work for you?

Can you provide your /etc/syslog* configs and the output of: ls -1d /etc/init.d/rc*.d/S*

We are using rsyslogd by default and it supports several nice features, that I may enable for 11.3. It is able to use a disk-assisted queue.

That is, we can improve the default setup I think -- I'll test it out.

Marius - Well this sounds interesting and hopeful! I have not dug into this very far so please bear with me... I was having troubles with my laptop initializing it's network interfaces (in particular the wireless one) and was searching through the messages logs file (and others) and noted nothing was being reported from the network daemon when it is started.. This lead me to do a bit of exploring of the inet.d startup sequence when I noted that the local file system daemon is first to be started, then the network daemon, then the remote file system, and finally the rsyslog daemon. I also noted that the rsyslog daemon was dependent on the network and remote file system daemons, hence that lead me to file this bug report, as I felt logging should be done earlier to the local file system and not entirely dependent on having the remote file system daemon or the network daemon running first. (Both of these could be logging to the local file system until the remote logging is available...) So, to answer your question, no - early syslogging is not working for me. I noticed the reference to it in the scripts, but also some comment about it not being fully tested or guaranteed to be functional. I also notice another conf file - rsyslog.early.conf that looks promising, but I have not tracked down where it is used. I do not have any syslog.conf files in /etc but do have the rsyslog.conf and rsyslog.early.conf file which I will attach for you. Also attached is the output of the ls command you requested... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=606972 http://bugzilla.novell.com/show_bug.cgi?id=606972#c9 --- Comment #9 from Marc Chamberlin 2010-05-26 18:18:39 UTC --- Created an attachment (id=364977) --> (http://bugzilla.novell.com/attachment.cgi?id=364977) Output from ls command showing rc*.d files -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=606972 https://bugzilla.novell.com/show_bug.cgi?id=606972#c11 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #11 from Dr. Werner Fink 2010-09-13 15:41:19 UTC --- Suppose this on as fixed -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.