| Summary: | rsync-2.6.2-r1 fails to start, looking for config file in wrong directory | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Aaron Riekenberg <aaron> |
| Component: | New packages | Assignee: | Martin Holzer (RETIRED) <mholzer> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | gustav.schaffter |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 49534 | ||
Same issue here, it will start, but wont read the conf file. Then u cant kill it because it doesnt know where the pid file is. *** Bug 49731 has been marked as a duplicate of this bug. *** fixed with rsync-2.6.2-r2.ebuild closing |
After I emerge rsync-2.6.2-r1, rsyncd looks for the configuration file /etc/rsyncd.conf instead of /etc/rsync/rsyncd.conf. Since /etc/rsyncd.conf is not created by the ebuild, rsyncd fails to start. Reproducible: Always Steps to Reproduce: 1. emerge =net-misc/rsync-2.6.2-r1 2. /etc/init.d/rsyncd start Actual Results: /var/log/daemon.log contains the following: May 2 09:41:41 files rsyncd[5792]: rsync: unable to open configuration file "/etc/rsyncd.conf": No such file or directory May 2 09:41:41 files rsyncd[5792]: rsync error: syntax or usage error (code 1) at clientserver.c(586) Also, ps shows rsync is not running. The problem here is the following call to sed in the src_unpack function in the ebuild: sed -i \ -e 's|/etc/rsyncd.conf|/etc/rsync/rsyncd.conf|g' \ rsync.h \ || die "sed rsync.h failed" rsync.h does not contain /etc/rsyncd.conf with rsync-2.6.2-r1, so this sed does nothing. I changed the call to econf in src_compile from this: econf \ $(use_with build included-popt) \ $(use_with acl acl-support) \ || die to this: econf \ $(use_with build included-popt) \ $(use_with acl acl-support) \ --with-rsyncd-conf=/etc/rsync/rsyncd.conf \ || die and it fixed the problem. It also seems a little less evil than using sed on a header file.