Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Monday 2008-07-07 at 15:52 -0400, Jose wrote:
Carlos E. R. wrote:
Or you could modify the first line of the script to
#!/bin/bash -x
so that it prints the entire lot to the screen when it runs and you can see what happens, hopefully.
Hi
I tried it the way from the script, but I only get the same message saying the following:
Let's see.
Starting syslog servicesstartproc: Empty pid file /var/run/syslogd.pid for /sbin/syslogd
This is the output for the /bash -x option:
vmware:/etc/init.d # ./syslog start
+ killproc -p /var/run/klogd.pid /sbin/klogd + test -s /var/run/syslogd.pid
This test checks if the file exists and is not empty - and it fails, because it is empty. This corresponds to this code:
if test -s ${syslog_use_pid} ; then killproc -p ${syslog_use_pid} ${syslog_use} echo -n "Re-" rm -f /var/lock/subsys/syslogd fi
So the killproc is not executed,, and the lock file (which exists) is not removed. Then it executes this code:
echo -n "Starting syslog services" test -z "$KERNEL_LOGLEVEL" && KERNEL_LOGLEVEL=1
corresponding to this output:
+ echo -n 'Starting syslog services' Starting syslog services+ test -z 1 + startproc -p /var/run/syslogd.pid /sbin/syslogd -r startproc: Empty pid file /var/run/syslogd.pid for /sbin/syslogd
So... you can manually delete that lock file, and see if the script runs. Then stop and start it again, and see if gets stuck again.
And then you could write a bugzilla to request suse adds code checking for an empty lock file in there ;-)
- -- Cheers, Carlos E. R.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux)
iD8DBQFIcp6RtTMYHG2NR9URAgNGAKCWAV62S0oVjbs29fYuUPm92R2q9QCgkoZK yMLxmb4CaAiwZrAVb44klJs= =ogjx -----END PGP SIGNATURE----- Hi Carlos,
No dice, I tried it and still does not work. I am suspecting something broken within syslogd, as I changed the parameter from -r to -rd and now it actually works using the script, I tried using without params and I still got a defunct process, it only likes to run regardless if using the script or not if I add the "d" parameter, weird, for now I can live with this till I find which is a similar switch on syslog-ng. Thanks Carlos for your time and help. Jose -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org