Bugzilla – Bug 113591
killproc doesn't kill rsync daemon
Last modified: 2009-06-04 09:11:56 UTC
And this is only the case for the rsyncd. Not for smbd or nmbd for example. This happens on an older P III 1.2 GHz system. gab:~ # rcrsyncd status Checking for rsync daemon: running gab:~ # rcrsyncd stop Shutting down rsync daemon done gab:~ # rcrsyncd status Checking for rsync daemon: running gab:~ # killproc -TERM /usr/sbin/rsyncd gab:~ # rcrsyncd status Checking for rsync daemon: running gab:~ # pkill rsyncd gab:~ # rcrsyncd status Checking for rsync daemon: unused
Also valid on a different system (AMD Athlon 900 MHz). Both systems are running 10.0 Beta 3.
Update to stable.
I know this report is ancient, but I'm seeing exactly the same or at least a very similar problem today on my openSUSE 11.0 installation. The problem, AFAICT, is caused by the 'startproc /usr/sbin/rsync --daemon' not writing a pidfile in /var/run/rsyncd.pid. This is presumably due to rsyncd detaching itself from its parent, which means startproc has nothing to write to the pidfile. The result is that rsyncd can be started with rcrsyncd, but not stopped. 'rcrsyncd stop' says it has stopped rsyncd, but it hasn't.
startproc does not write pid files, this is the job of the daemon its self. To stop a daemon simply use killproc /usr/sbin/rsyncd and it will be stopped. This is done in /etc/init.d/rsyncd. If it does not work the wrong binray is used. Beside this on openSUSE 11.1 it works: # rcrsyncd start Starting rsync daemon done # rcrsyncd status Checking for rsync daemon: running # rcrsyncd stop Shutting down rsync daemon done # rcrsyncd status Checking for rsync daemon: unused