[opensuse-factory] Well known /var/log/boot.msg even with systemd
Hi, during debugging I've missed the /var/log/boot.msg therefore I've written a replacment for /etc/init.d/boot.klog as well as for the current symbolic link /lib/systemd/system/klog.service which currently points forward to /dev/null. I'd like to suppose the attached replacment for this link. With this service file the well known /var/log/boot.msg will be created. By using dmesg(1) the normal kernel and boot messages handled by systemd will not disappear. Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr
Le vendredi 19 août 2011 à 15:22 +0200, Dr. Werner Fink a écrit :
Hi,
during debugging I've missed the /var/log/boot.msg therefore I've written a replacment for /etc/init.d/boot.klog as well as for the current symbolic link /lib/systemd/system/klog.service which currently points forward to /dev/null.
I'd like to suppose the attached replacment for this link. With this service file the well known /var/log/boot.msg will be created.
By using dmesg(1) the normal kernel and boot messages handled by systemd will not disappear.
Sounds good. I'll integrate it in my next push for Base:System systemd. -- Frederic Crozat <fcrozat@novell.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Le vendredi 19 août 2011 à 15:38 +0200, Frederic Crozat a écrit :
Le vendredi 19 août 2011 à 15:22 +0200, Dr. Werner Fink a écrit :
Hi,
during debugging I've missed the /var/log/boot.msg therefore I've written a replacment for /etc/init.d/boot.klog as well as for the current symbolic link /lib/systemd/system/klog.service which currently points forward to /dev/null.
I'd like to suppose the attached replacment for this link. With this service file the well known /var/log/boot.msg will be created.
By using dmesg(1) the normal kernel and boot messages handled by systemd will not disappear.
Sounds good.
I'll integrate it in my next push for Base:System systemd.
After thinking again, it is probably better to put the file into klogd package. I'll remove the /dev/null symlink from systemd package and I let you put the service file in klogd package. -- Frederic Crozat <fcrozat@suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Fri, Aug 19, 2011 at 05:37:00PM +0200, Frederic Crozat wrote:
Le vendredi 19 août 2011 à 15:38 +0200, Frederic Crozat a écrit :
Le vendredi 19 août 2011 à 15:22 +0200, Dr. Werner Fink a écrit :
Hi,
during debugging I've missed the /var/log/boot.msg therefore I've written a replacment for /etc/init.d/boot.klog as well as for the current symbolic link /lib/systemd/system/klog.service which currently points forward to /dev/null.
I'd like to suppose the attached replacment for this link. With this service file the well known /var/log/boot.msg will be created.
By using dmesg(1) the normal kernel and boot messages handled by systemd will not disappear.
Sounds good.
I'll integrate it in my next push for Base:System systemd.
After thinking again, it is probably better to put the file into klogd package.
I'll remove the /dev/null symlink from systemd package and I let you put the service file in klogd package.
I'm currently thinking about splitting klogd package into two parts one for klogd it's self and one for the script/unit files for the various system loggers. Also we should enable the builtin klog of syslog-ng as with this only the old syslogd would require the old klogd package. Marius? What do you think about? Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (2)
-
Dr. Werner Fink -
Frederic Crozat