bug#49190: uptime returns an incorrect (18801 days) number of days on OsX

[Manson Thomas]

Hi Paul,

same result (see below)

I have two other macbook :
* one on Catalina version (where BigSur is not offered), with
coreutils version 8.32 (so the same version), and that produces a
correct uptime value
* one on BigSur version, with coreutils v8.32, and that produces a
correct uptime value

The only difference with the faulty mac is that I've a company
firewall (or security solution named crowdstrike inc that requires the
system to be restarted for an update)

So I've restarted my mac, and then uptime was returning correct
values... (after restart, and after latest BigSur update)

Sorry to have bothered you :(

 $  sudo dtruss  /usr/bin/uptime
Password:
dtrace: system integrity protection is on, some features will not be available

dtrace: failed to execute /usr/bin/uptime: (os/kern) failure

 $    /usr/bin/uptime
17:55  up 38 days,  8:11, 3 users, load averages: 1.64 1.96 2.12

Cordialement,
Thomas Manson.


On Thu, Jun 24, 2021 at 5:54 PM Paul Eggert <eggert@cs.ucla.edu> wrote:
>
> On 6/24/21 1:26 AM, Manson Thomas wrote:
> >   $  sudo dtruss /usr/bin/uptime
> > dtrace: system integrity protection is on, some features will not be 
> > available
> >
> > dtrace: failed to execute /usr/bin/uptime: (os/kern) failure
>
> Can you copy /usr/bin/uptime to /tmp/uptime and then dtruss /tmp/uptime?