Am 14.04.2013 02:55, schrieb Cristian Rodríguez:
Ok Stefan:
So your syslog-ng losses messages on boot.. can you please test the following unit file and report back ?
save it as "syslog-ng.service" in /etc/systemd/system/
[Unit] Description=System Logging Service Requires=var-run.mount Requires=syslog.socket After=var-run.mount Conflicts=rsyslog.service syslogd.service
[Service] Environment=SYSLOG_NG_PARAMS= ExecStartPre=/usr/sbin/syslog-ng-service-prepare EnvironmentFile=-/etc/sysconfig/syslog ExecStart=/usr/sbin/syslog-ng -F $SYSLOG_NG_PARAMS ExecReload=/bin/kill -HUP $MAINPID StandardOutput=null
[Install] WantedBy=multi-user.target Alias=syslog.service
systemctl --system daemon-reload
test, test, test..
Ok, changed this, next reboot date depends on Kernel:HEAD having x86_64 relevant updates I found that /etc/systemd/system contains lots of directories and symlinks that do not belong to any package. And then there is one file that also does not belong to any package: systemd-random-seed-load.service it's dated Jan 29 2013, I'm pretty sure I did not create it manually and it fails. To get back on topic in opensuse-packaging: should we mark all those /etc/systemd/system/dbus-org.bluez.service and friends as %ghost in the packages so that one actually can find out if this is a system file or not? I'm usually inclined to remove everything not known to RPM from my systems, but I figured that this might break my system even more.... :-) -- Stefan Seyfried "If your lighter runs out of fluid or flint and stops making fire, and you can't be bothered to figure out about lighter fluid or flint, that is not Zippo's fault." -- bkw -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org