[systemd-devel] systemd-logind bug in systemd v35

[Lennart Poettering]

On Wed, 05.10.11 15:34, Albert Strasheim (fullung at gmail.com) wrote:

> > That looks as if somehow the sessions are leaked there. Can you do a
> > fuser -v on the .ref fifos as root? That should tell us if those fds are
> > still referenced.
> 
> # fuser -v *.ref
>                      USER        PID ACCESS COMMAND
> 1310.ref:            root      23311 F.... systemd-logind
> 1368.ref:            root      23311 f.... systemd-logind
> 1369.ref:            root      23311 f.... systemd-logind
> 1370.ref:            root      23311 F.... systemd-logind
> 1371.ref:            root      23311 f.... systemd-logind
> 1372.ref:            root      23311 f.... systemd-logind
> 1373.ref:            root      23311 f.... systemd-logind
> 1374.ref:            root      23311 f.... systemd-logind
> 1375.ref:            root      23311 f.... systemd-logind
> 1376.ref:            root      23311 f.... systemd-logind
> 1377.ref:            root      23311 f.... systemd-logind
> 1378.ref:            root      23311 f.... systemd-logind
> 1379.ref:            root      23311 F.... systemd-logind
> 1380.ref:            root      23311 F.... systemd-logind
> 
> etc.

Hmm, that suggests that systemd-logind never received an EOF on those
fds, which is really weird.

Or actually it shows with F that it has those fds open for writing which
should never happen. Weird. I'll try to reproduce this here.

Lennart

-- 
Lennart Poettering - Red Hat, Inc.