On Mon, Nov 28, 2011 at 9:02 AM, David Highley <dhigh...@highley-recommended.com> wrote: > "David Highley wrote:" >> "T.C. Hollingsworth wrote:" >> > For more information on converting inetd services to systemd units, see: >> > http://0pointer.de/blog/projects/inetd.html > > It appears that this example maybe out of date. Looks like the argument > StandardInput is no longer valid, according to: > http://0pointer.de/public/systemd-man/systemd.service.html
StandardInput is explained in "man systemd.exec": http://0pointer.de/public/systemd-man/systemd.exec.html Unit file syntax may have fields added, but should never have fields removed except in rare circumstances, at which point they will be subject to a long deprecation process. > We also do not see where the "@" is being used in any of the scripts > for the names. The supplied sshd.service looks different and does not > have an accompanying sshd.socket file. So we really do not understand > how this works at this point. The "@" syntax is described in detail here: http://0pointer.de/blog/projects/instances.html Fedora's openvpn@.service and getty@.service use it, perhaps others too. sshd supports being used both as an inetd-style daemon and a regular daemon. Fedora installs it as a regular daemon. -T.C. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
