Am 17.03.2011 02:32, schrieb Lennart Poettering: > On Thu, 17.03.11 02:21, Mirco Tischler (mircotisch...@gmx.net) wrote: >>> Your sshd seems to return exit with a non-zero exit code just indicating >>> a failure of some kind. use "ExecStart=-/foo/bar" instead of >>> "ExecStart=/foo/bar" to spawn a process and ignore if it fails. >>> >>> Lennart >>> >> The most likely failure here is an authentication failure. sshd exits >> with exit code 254(afair) in that case if in inet mode. This caused the >> very same problem (sshd.socket shutting down) for me on a machine that >> was accessable from the internet where I get a few hundred failed login >> attempts per day. > I think it is probably wise to use ExecStart=- on all instantiated > socket services. Since failed services are not GC'ed you might otherwise > end up collecting up quite a number of failed sshd@ instances until the > limit is reached and further clients will be refused. > > Lennart > Yup, I agree on that. Just wanted to make a suggestion were all those failed instances may come from :)
Thanks Mirco
signature.asc
Description: OpenPGP digital signature
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
