On 2013-06-10 02:23, Cristian Rodríguez wrote:
El 09/06/13 20:18, Carlos E. R. escribió:
That's what happened earlier, but it is not happening now. Mine is not looping fast enough for systemd to think it is looping.
Ok, how exactly did you proceed ? I did exactly what you mentioned in your email and get the expected result.
I edited in that line, restarted service, bang. Just like that. The file has more entries, of course, but that's the one that causes the problem.
Telcontar:~ # systemctl restart rsyslog.service Telcontar:~ #
Telcontar:~ # systemctl status rsyslog.service rsyslog.service -
show your unit file ;)
it should read:
cat /usr/lib/systemd/system/rsyslog.service
[Unit] Description=System Logging Service Requires=var-run.mount Requires=syslog.socket After=var-run.mount
[Service] Environment=RSYSLOGD_PARAMS= ExecStartPre=/usr/sbin/rsyslog-service-prepare EnvironmentFile=-/etc/sysconfig/syslog ExecStart=/usr/sbin/rsyslogd -n $RSYSLOGD_PARAMS ExecReload=/bin/kill -HUP $MAINPID StandardOutput=null
[Install] WantedBy=multi-user.target Alias=syslog.service
If it doesnt read this way, save it as /etc/systemd/system/rsyslog.service and issue
# systemctl daemon-reload # systemctl reenable rsyslog.service
I have not touched it. i see differences, but I swear I have not touched it myself.
cer@Telcontar:~> l /usr/lib/systemd/system/rsyslog.service -rw-r--r-- 1 root root 475 Apr 29 17:37 /usr/lib/systemd/system/rsyslog.service cer@Telcontar:~> cat /usr/lib/systemd/system/rsyslog.service [Unit] Description=System Logging Service Requires=var-run.mount syslog.target After=var-run.mount Before=syslog.target Conflicts=syslog-ng.service syslogd.service
[Service] Environment=RSYSLOGD_PARAMS= ExecStartPre=/usr/sbin/rsyslog-service-prepare EnvironmentFile=-/etc/sysconfig/syslog ExecStart=/usr/sbin/rsyslogd -n $RSYSLOGD_PARAMS ExecReload=/bin/kill -HUP $MAINPID Sockets=syslog.socket StandardOutput=null
[Install] WantedBy=multi-user.target Alias=syslog.service cer@Telcontar:~>
I can provoke the failure and get output from some log or command showing whatever is the problem, or hook a trace to it. -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org