El 16/04/13 21:11, Marcos Felipe Rasia de Mello escribió:
systemd[1]: Trying to enqueue job rsyslog.service/stop/replace systemd[1]: Installed new job rsyslog.service/stop as 408 systemd[1]: Enqueued job rsyslog.service/stop as 408 systemd[1]: Stopping System Logging Service...
OK, trying to stop... # Package removal, not upgrade /usr/bin/systemctl --no-reload disable rsyslog.service > /dev/null 2>&1 || : /usr/bin/systemctl stop rsyslog.service > /dev/null 2>&1 || : --> here...
systemd[1]: syslog.socket got notified about service death (failed permanently: no) systemd[1]: syslog.socket changed running -> listening
waiting for requests on the socket, as expected..
systemd[1]: rsyslog.service changed running -> stop-sigterm
stop signal sent..(most deamons catch signals to do house keeping before going away..) buuuuut units still there, systemd has been told by rpm post scriptlets not to reload its configuration on disable.. hahah! <evil grin> (drum roll)
systemd[1]: Incoming traffic on syslog.socket
Still sending data...nothing wrong with that but...
systemd[1]: Trying to enqueue job rsyslog.service/start/replace systemd[1]: syslog.socket got notified about service death (failed permanently: no)
As --no-reload was passed, systemd assumes that "you know what are you doing" you decided not to provide it "fresh" information about the fact there is no syslog implementation anymore..it tries to do what it should.. ta dah! FAIL. :D For this particular case --no-reload is not adequate.. but rpm scriptlets are generic ;) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org