when startup delays become bugs

Lennart Poettering mzerqung at 0pointer.de
Wed May 15 15:44:34 UTC 2013

On Wed, 15.05.13 10:05, Chris Adams (linux at cmadams.net) wrote:

> Once upon a time, Matthew Miller <mattdm at fedoraproject.org> said:
> > In that bug you suggest that administrators could change back to standalone
> > mode. Given that what you say about frequency of access is true (even on
> > systems where ssh login is a primary activity, time between accesess is
> > generally on a human scale rather hundreds per second), is there a
> > disadvantage to socket activation beyond a very slight delay in the first
> > access?
> Well, SSH connection rate is on "human scale" until your system is the
> target of a scan, which can result in at least dozens per second.

Note that systemd puts a (configurable) limit on the number of
concurrent connections, much like sshd does it, so there's very little
difference... Also ssh forks of per-connection processes too, so the
difference is probably even smaller...


Lennart Poettering - Red Hat, Inc.

More information about the devel mailing list