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

[Albert Strasheim]

On Wed, Oct 5, 2011 at 2:48 PM, Lennart Poettering
<lennart at poettering.net> wrote:
> On Wed, 05.10.11 10:56, Albert Strasheim (fullung at gmail.com) wrote:
>> On Wed, Oct 5, 2011 at 1:40 AM, Lennart Poettering
>> <lennart at poettering.net> wrote:
>> > What is the contents of /run/systemd/sessions/?
>> There's about 2000 files in that directory. Filenames with numbers and
>> the same number.ref.
>> This is even when no-one is logged into the system.
> 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.

Regards

Albert