Lennart Poettering <lenn...@poettering.net> writes: > On Wed, 15.10.14 11:07, Jan Synacek (jsyna...@redhat.com) wrote: > >> Hello, >> >> in the documentation for systemd.service, under Type= option, it reads: >> >> Behavior of oneshot is similar to simple; however, it is expected that the >> process has to exit before systemd starts follow-up unit RemainAfterExit= >> is particularly useful for this type of service. This is the implied >> default >> if neither Type= or ExecStart= are specified. >> >> I don't think that the part about not specifying ExecStart is correct. If >> there is no ExecStart in the service file, I get an error. > > As pointed out by Mantas this limitation has been removed a while back. > >> >> Also, under Sockets= option: >> >> ... >> Also note that a different service may be activated on incoming >> traffic than that which inherits the sockets. >> ... >> >> I had to reread that sentence about 10 times to actually get it. I'd say >> that rewording it would be benefitial. > > I tried to reword it a bit now in git. Not sure it's a ton more > understandable though... > > Lennart
It's a bit better, at least for me, thank you. -- Jan Synacek Software Engineer, Red Hat
signature.asc
Description: PGP signature
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
