Bug with procps-ng or systemd?
 

/var/log/utmp is not being used.

Updated procps-ng on the 24th, systemd 192 update on the 27th, but have
only just noticed this.

Running a "w" command no longer shows current logged in users.

An strace of /usr/bin/w shows:

access("/var/run/utmpx", F_OK) = -1 ENOENT
(No such file or directory)
open("/var/run/utmp", O_RDONLY|O_CLOEXEC) = -1 ENOENT
(No such file or directory)
access("/var/run/utmpx", F_OK) = -1 ENOENT
(No such file or directory)
open("/var/run/utmp", O_RDONLY|O_CLOEXEC) = -1 ENOENT
(No such file or directory)

I have searched FS but haven't found anything relevant, should a bug be
lodged against procps-ng or systemd?

--
Simon Perry (aka Pezz)

Bug with procps-ng or systemd?
 

ri, Sep 28, 2012 at 3:14 PM, Simon Perry <arch@sanxion.net> wrote:
> /var/log/utmp is not being used.
>
> Updated procps-ng on the 24th, systemd 192 update on the 27th, but have
> only just noticed this.
>
> Running a "w" command no longer shows current logged in users.
>
> An strace of /usr/bin/w shows:
>
> access("/var/run/utmpx", F_OK) = -1 ENOENT
> (No such file or directory)
> open("/var/run/utmp", O_RDONLY|O_CLOEXEC) = -1 ENOENT
> (No such file or directory)
> access("/var/run/utmpx", F_OK) = -1 ENOENT
> (No such file or directory)
> open("/var/run/utmp", O_RDONLY|O_CLOEXEC) = -1 ENOENT
> (No such file or directory)
>
> I have searched FS but haven't found anything relevant, should a bug be
> lodged against procps-ng or systemd?
>
> --
> Simon Perry (aka Pezz)
>

https://bugs.archlinux.org/task/31705 ?

Bug with procps-ng or systemd?
 

Apologies,

Just noticed the "[arch-general] utmp MIA" thread and FS#31705 as
pointed out by Tom in said thread.

(I blame Friday night boozing)

--
Simon Perry (aka Pezz)