[systemd-devel] systemd-logind bug in systemd v35
lennart at poettering.net
Wed Oct 5 05:50:13 PDT 2011
On Wed, 05.10.11 11:04, Albert Strasheim (fullung at gmail.com) wrote:
> On Wed, Oct 5, 2011 at 1:40 AM, Lennart Poettering
> <lennart at poettering.net> wrote:
> > On Tue, 04.10.11 15:40, Albert Strasheim (fullung at gmail.com) wrote:
> >> Hello all
> >> I think we've found a bug in systemd-logind with systemd v35
> >> (specifically, systemd-35-1.fc16.x86_64.rpm).
> >> After a few thousand ssh logins, we start seeing stuff like this in
> >> /var/log/secure:
> > After a few thousand parallel ssh logins or one after the other?
> Forgot to answer this one: this is only with a few parallel logins,
> but many logins over a period of hours.
> Which raises the question: what is systemd-logind going to do when
> more than 1024 users log in to a machine at the same time?
The admin should probably increase the resource limit for it. Maybe we
should do that by default.
> Which raises the more general question: what will other services like
> systemd-stdout-syslog-bridge do when the number of processes that log
> go into the hundreds? I haven't thought about it carefully, but there
> seems to be some cases where one could run into the default limit of
> 1024 open files.
Well, I guess every software has that problem. And the answer is always
the same: increase the limit.
Lennart Poettering - Red Hat, Inc.
More information about the systemd-devel