Bug 39049

Summary:	rsync ebuild is broken - fails to include a config path!
Product:	Gentoo Linux	Reporter:	Stephen Bosch <posting>
Component:	[OLD] Server	Assignee:	Gentoo Linux bug wranglers <bug-wranglers>
Status:	RESOLVED DUPLICATE
Severity:	critical
Priority:	High
Version:	1.4
Hardware:	x86
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Stephen Bosch 2004-01-22 10:07:52 UTC

rsyncd won't start properly because there is no configuration file specified by default. Once a start is attempted, runscript thinks the process is running and won't attempt a restart, even though there is no rsync process.

Reproducible: Always
Steps to Reproduce:
1.execute '/etc/init.d/rsync start'
2.
3.

Actual Results:  
root@moose:/etc/conf.d# /etc/init.d/rsyncd start
 * WARNING:  "rsyncd" has already been started.
root@moose:/etc/conf.d# /etc/init.d/rsyncd stop
 * Stopping rsyncd...
cat: /var/run/rsyncd.pid: No such file or directory
kill: usage: kill [-s sigspec | -n signum | -sigspec] [pid | job]... or kill -l
[sigspec]                                                                 [ !! ]

root@moose:/etc/conf.d# /etc/init.d/rsyncd status
 * status:  started
root@moose:/etc/conf.d# ps -ef | grep rsync
root@moose:/etc/conf.d#

Expected Results:  
rsync should stop and start when commanded.

Comment 1 Martin Holzer (RETIRED) gentoo-dev

2004-01-22 11:14:51 UTC


*** This bug has been marked as a duplicate of 39052 ***