Re: Bullseye - who and users return nothing

On Tue 25 Jan 2022, at 13:11, Greg Wooledge wrote: > On Tue, Jan 25, 2022 at 01:06:42PM +, Gareth Evans wrote: >> Just realised I gave contradicting info earlier - I said both that I >> upgraded from Buster (which is literally true) and that >> >> "But for root on ZFS per >> >>

Re: Bullseye - who and users return nothing

Jan 25, 2022, 13:06 by donots...@fastmail.fm: > both return nothing, with or without sudo. > Can anyone replicate this or suggest what may have happened? I'm fairly sure I've used who since upgrading from Buster. Also upgraded from Buster but can't reproduce the issue. Both

Re: Bullseye - who and users return nothing

On Tue, Jan 25, 2022 at 01:06:42PM +, Gareth Evans wrote: > Just realised I gave contradicting info earlier - I said both that I upgraded > from Buster (which is literally true) and that > > "But for root on ZFS per > >

Re: Bullseye - who and users return nothing

On Tue 25 Jan 2022, at 01:31, Gareth Evans wrote: > On Mon 24 Jan 2022, at 12:45, Greg Wooledge wrote: >> On Mon, Jan 24, 2022 at 09:51:05AM +, Gareth Evans wrote: >>> I've just noticed that: >>> >>> $ who >>> >>> and >>> >>> $ users >>> >>> both return nothing, with or without sudo. >>

Re: Bullseye - who and users return nothing

On Tue 25 Jan 2022, at 10:47, Andrei POPESCU wrote: > On Ma, 25 ian 22, 04:03:17, Gareth Evans wrote: >> >> Googling "Detected unsafe path transition during canonicalization" led me to >> >> https://bbs.archlinux.org/viewtopic.php?id=260924 >> >> where a user sees this error because / is

Re: Bullseye - who and users return nothing

On Ma, 25 ian 22, 04:03:17, Gareth Evans wrote: > > Googling "Detected unsafe path transition during canonicalization" led me to > > https://bbs.archlinux.org/viewtopic.php?id=260924 > > where a user sees this error because / is owned by the user rather than root. > > Lo and behold > > $

Re: Bullseye - who and users return nothing

On Tue 25 Jan 2022, at 04:50, David Wright wrote: > On Tue 25 Jan 2022 at 04:22:39 (+), Gareth Evans wrote: >> On Tue 25 Jan 2022, at 04:10, Polyna-Maude Racicot-Summerside >> wrote: >> > On 2022-01-24 23:03, Gareth Evans wrote: >> >> Jan 25 01:46:52 qwerty systemd-tmpfiles[1340]: Detected

Re: Bullseye - who and users return nothing

On Tue 25 Jan 2022 at 04:22:39 (+), Gareth Evans wrote: > On Tue 25 Jan 2022, at 04:10, Polyna-Maude Racicot-Summerside > wrote: > > On 2022-01-24 23:03, Gareth Evans wrote: > >> Jan 25 01:46:52 qwerty systemd-tmpfiles[1340]: Detected unsafe path > >> transition / → /var during

Re: Bullseye - who and users return nothing

On Tue 25 Jan 2022, at 04:10, Polyna-Maude Racicot-Summerside wrote: > On 2022-01-24 23:03, Gareth Evans wrote: >> On Tue 25 Jan 2022, at 03:28, Greg Wooledge wrote: >>> On Tue, Jan 25, 2022 at 03:06:00AM +, Gareth Evans wrote: On Tue 25 Jan 2022, at 03:02, Gareth Evans wrote: >

Re: Bullseye - who and users return nothing

On 2022-01-24 23:03, Gareth Evans wrote: > On Tue 25 Jan 2022, at 03:28, Greg Wooledge wrote: >> On Tue, Jan 25, 2022 at 03:06:00AM +, Gareth Evans wrote: >>> On Tue 25 Jan 2022, at 03:02, Gareth Evans wrote: On Tue 25 Jan 2022, at 02:54, Greg Wooledge wrote: > A google search

Re: Bullseye - who and users return nothing

On Tue 25 Jan 2022, at 03:28, Greg Wooledge wrote: > On Tue, Jan 25, 2022 at 03:06:00AM +, Gareth Evans wrote: >> On Tue 25 Jan 2022, at 03:02, Gareth Evans wrote: >> > On Tue 25 Jan 2022, at 02:54, Greg Wooledge wrote: >> >> A google search led me to

Re: Bullseye - who and users return nothing

On Tue, Jan 25, 2022 at 03:06:00AM +, Gareth Evans wrote: > On Tue 25 Jan 2022, at 03:02, Gareth Evans wrote: > > On Tue 25 Jan 2022, at 02:54, Greg Wooledge wrote: > >> A google search led me to > >> which says that the /run/utmp file is supposed to

Re: Bullseye - who and users return nothing

On Tue 25 Jan 2022, at 03:02, Gareth Evans wrote: > On Tue 25 Jan 2022, at 02:54, Greg Wooledge wrote: >> On Tue, Jan 25, 2022 at 01:31:35AM +, Gareth Evans wrote: >>> /var/run$ sudo touch utmp >>> /var/run$ sudo chown root:utmp utmp >>> /var/run$ sudo chmod 664 utmp >>> /var/run$ ls -l utmp

Re: Bullseye - who and users return nothing

On Tue 25 Jan 2022, at 02:54, Greg Wooledge wrote: > On Tue, Jan 25, 2022 at 01:31:35AM +, Gareth Evans wrote: >> /var/run$ sudo touch utmp >> /var/run$ sudo chown root:utmp utmp >> /var/run$ sudo chmod 664 utmp >> /var/run$ ls -l utmp >> -rw-rw-r-- 1 root utmp 0 Jan 25 00:08 utmp >>

Re: Bullseye - who and users return nothing

On Tue, Jan 25, 2022 at 01:31:35AM +, Gareth Evans wrote: > /var/run$ sudo touch utmp > /var/run$ sudo chown root:utmp utmp > /var/run$ sudo chmod 664 utmp > /var/run$ ls -l utmp > -rw-rw-r-- 1 root utmp 0 Jan 25 00:08 utmp > /var/run$ who > /var/run$ > [logout, login] > /var/run$ ls -l

Re: Bullseye - who and users return nothing

On Tue 25 Jan 2022, at 01:31, Gareth Evans wrote: > On Mon 24 Jan 2022, at 12:45, Greg Wooledge wrote: >> On Mon, Jan 24, 2022 at 09:51:05AM +, Gareth Evans wrote: >>> I've just noticed that: >>> >>> $ who >>> >>> and >>> >>> $ users >>> >>> both return nothing, with or without sudo. >>

Re: Bullseye - who and users return nothing

On Mon 24 Jan 2022, at 12:45, Greg Wooledge wrote: > On Mon, Jan 24, 2022 at 09:51:05AM +, Gareth Evans wrote: >> I've just noticed that: >> >> $ who >> >> and >> >> $ users >> >> both return nothing, with or without sudo. > >> Can anyone replicate this or suggest what may have happened?

Re: Bullseye - who and users return nothing

On Mon, Jan 24, 2022 at 09:51:05AM +, Gareth Evans wrote: > I've just noticed that: > > $ who > > and > > $ users > > both return nothing, with or without sudo. > Can anyone replicate this or suggest what may have happened? I'm fairly sure > I've used who since upgrading from Buster.

Bullseye - who and users return nothing

Hello, I've just noticed that: $ who and $ users both return nothing, with or without sudo. $ sudo strace who access("/var/run/utmpx", F_OK) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/var/run/utmp", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)