GNU bug report logs - #24551
who doesn't read what man page says it does, so doesn't work

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 24551 in the body.
You can then email your comments to 24551 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: "L. A. Walsh" <coreutils <at> tlinx.org>
To: bug-coreutils <at> gnu.org
Subject: who doesn't read what man page says it does, so doesn't work
Date: Mon, 26 Sep 2016 18:40:29 -0700

coreutils-8.23 x64
manpage says:
      If  FILE is not specified, use /var/run/utmp.  /var/log/wtmp as 
FILE is
      common.  If ARG1 ARG2 given, -m presumed: 'am i'  or  'mom  
likes'  are
      usual.

   Behavior says:
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)
close(1)                                = 0
close(2)                                = 0
exit_group(0)                           = ?
+++ exited with 0 +++

---
just so happens my 'who' record is in /var/log/wtmp, and hacking in
a softlink on the ephemeral /var/run/utmp to the 2nd listed location will
make the 'who' command function until the next reboot.

Has this been fixed (or is this a suse special)?  That it accesses
the same file twice in a row instead of two separate files seems a
bit odd.

Message #8 received at 24551 <at> debbugs.gnu.org (full text, mbox):

From: Assaf Gordon <assafgordon <at> gmail.com>
To: "L. A. Walsh" <coreutils <at> tlinx.org>, 24551 <at> debbugs.gnu.org
Subject: Re: bug#24551: who doesn't read what man page says it does, so
 doesn't work
Date: Sun, 28 Oct 2018 01:01:28 -0600

tags 24551 notabug
close 24551
stop

(triaging old bugs)

It seems your message was lost and not replied to in 2 years.
Sorry about that.

On 2016-09-26 7:40 p.m., L. A. Walsh wrote:
> manpage says:
>   If  FILE is not specified, use /var/run/utmp.  /var/log/wtmp as FILE is
>   common.
[...]
>     Behavior says:
> 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)

This seems like the behavior is exactly as described:
The manual says "/var/run/utmp",
and the open syscall was performed on "/var/run/utmp"

As such, I'm marking this as 'notabug'.
Discussion can continue by replying to this thread.

-assaf

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.