View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0007542 | CentOS-7 | rsync | public | 2014-08-28 20:58 | 2014-08-29 14:38 |
Reporter | dmaziuk | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | always |
Status | new | Resolution | open | ||
Product Version | 7.0-1406 | ||||
Summary | 0007542: missing /etc/xinetd.d/rsync | ||||
Description | rsyncd can be run from xinetd or standalone. Only standalone config is included in centos 7. Previously rsync shipped with (disabled) xinetd config. | ||||
Tags | No tags attached. | ||||
abrt_hash | |||||
URL | |||||
or is it supposed to be handled by systemd now and its default is to exit after its done? Are we supposed to know that? | |
It is handled by systemd now via /usr/lib/systemd/system/rsyncd.service It sources /etc/rsyncd.conf and runs via /usr/bin/rsync --daemon --no-detach "$OPTIONS" While it's not explicitly stated or documented (even upstrream) anywhere, yes. There is some expectation that the admin knows this. |
|
google tells me "multiple instance" services should have a '@': rsyncd@.service. This doesn't so it's still b0rk3d. Since xinetd has a dozen access control features systemd does not, I believe switching rsync from systemd is a regression. Either way there's no reason to not ship /etc/xinetd.d/rsync with the rpm. |
|
> ... switching rsync from systemd is a regression Sorry, from xinetd to systemd. |
|