Create an rsyncd.service fedora 16

David Highley dhighley at
Mon Nov 28 20:00:50 UTC 2011

"T.C. Hollingsworth wrote:"
> On Mon, Nov 28, 2011 at 10:42 AM, David Highley
> <dhighley at> wrote:
> > "David Highley wrote:"
> >> Looked at the openvpn at .service script and see the type=forking
> >> statement. We added this but with the above issue not able to tell if it
> >> helped. The document on systemd.exec still leaves us wondering where and
> >> which file to insert the StandardInput statement. Will look at more
> >> scripts to see if we can determine the correct location.
> "Type=forking" doesn't work with inetd-style daemons; by definition
> they cannot fork.  openvpn isn't an inetd-style service, it uses the @
> in a different manner, because it can be started with more than one
> configuration file, as opposed to more than one socket like
> rsyncd/inetd services.
> StandardInput does go into the [Service] section of the .service file;
> that was done correctly.
> > Just to be clear we now have:
> <snipped>
> I double-checked a few details and there are some other things that
> need to be fixed:
> EnvironmentFile is incorrect.  EnvironmentFile is generally used for
> things in /etc/sysconfig, and can only contain a list of environment
> variables that are passed to the Exec lines.  (e.g. you might have
> "PORT=8080" in /etc/sysconfig/foobar and "ExecStart=/usr/sbin/foobar
> -p $PORT").  This line can be removed.
> inetd-style services don't need an [Install] section in the .service
> file at all; that's only necessary for services that use systemd's new
> socket activation features.  So that section can also be removed.
> "" is implicit in F16, it's a part of
> DefaultDependencies.  So it can be safely removed, but doesn't hurt
> anything if it stays.  (I mention this only because I removed it out
> of habit in my below example, it doesn't matter if it stays or goes.)
> So, your final files should look like:
> That should work just fine.  Remember, you need to operate on the
> socket, not the service.  systemd will start the service itself when
> users connect to it.  So, to enable the socket to start when your
> computer starts, run:
> systemctl enable rsyncd.socket

It is now working, operating on rsyncd.socket was not obvious to us
instead of the service. Made the last few changes as well to clean it
up. We greatly appreciate the information and help in getting this to

> To start the rsyncd socket so accepts connections right now, run:
> systemctl start rsyncd.socket
> -T.C.
> -- 
> users mailing list
> users at
> To unsubscribe or change subscription options:
> Guidelines:
> Have a question? Ask away:

More information about the users mailing list