You are not logged in.
So I got rsyncd via pacman, no problem. Installed it, and started it:
[root@unas rc.d]# ./rsyncd start
:: Starting rsyncd [BUSY] ./rsyncd: line 13: pgrep: command not found
[DONE]It seemed a little odd to me that pacman would not have detected the dependancy (pgrep) and taken care of it. Oh well. So I installed procps-3.2.7-4 to alleviate the problem. I then try to restart rsyncd:
[root@unas rc.d]# ./rsyncd restart
:: Stopping rsyncd [BUSY] kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
[FAIL]
:: Starting rsyncd [FAIL]Uh oh, this looks like bad news. Lets try again:
[root@unas rc.d]# ./rsyncd start
:: Starting rsyncd [FAIL]Suggestions anyone?
Last edited by relinquish (2008-03-05 20:59:27)
Offline
There's probably a stray /var/run/rsyncd.pid file which was caused by the pgrep error. If so, removing it manually. Check also if the daemon is not already running:
$ ps aux |grep rsync
If so, kill it manually. After that, try starting the daemon again.
About the missing procps dependency, procps is part of base. It is generally assumed that everyone has all the base packages installed, except for advanced users who know what they are doing. Anyway, I'll add it to the dependencies.
Offline
At first we have a fail:
[root@unas rc.d]# ls /var/run/rsyncd.pid
ls: cannot access /var/run/rsyncd.pid: No such file or directory
[root@unas rc.d]# ps aux | grep rsync
root 6794 0.0 0.1 1816 580 pts/0 R+ 22:07 0:00 grep rsync
[root@unas rc.d]# ./rsyncd start
:: Starting rsyncd [FAIL]
[root@unas rc.d]#I was able to start the process manually (/usr/bin/rsync --daemon), so the only remaining option was checking /var/run/daemons. Sure enough, rm'ing /var/run/daemons/rsyncd worked like a charm.
Offline