Hi,
This change in behaviour of time(1), both bash's built-in one and GNU
time, on the new Pi 5 machine with Raspbian surprised me.
First, here's the old behaviour on a different machine. Running
timeout(1) without or with sudo makes no difference: time sees a rough
35/65 split between userspace and system call.
$ lsb_release -a | cat
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye
$
$ time timeout 1 yes >/dev/null
real 0m1.002s
user 0m0.386s
sys 0m0.616s
$
$ time sudo timeout 1 yes >/dev/null
real 0m1.009s
user 0m0.359s
sys 0m0.649s
$
But on the new machine, I seem to be timing just sudo.
$ lsb_release -a | cat
Distributor ID: Debian
Description: Debian GNU/Linux 13 (trixie)
Release: 13
Codename: trixie
$
$ time timeout 1 yes >/dev/null
real 0m1.002s
user 0m0.237s
sys 0m0.764s
$
$ time sudo timeout 1 yes >/dev/null
real 0m1.015s
user 0m0.010s
sys 0m0.004s
$
Anyone know why? Probably a security improvement somehow.
I was doing my routine ‘sudo dd’ to scrub storage and noticed the output
of GNU's ‘time -v’ was missing much information.
--
Cheers, Ralph.
--
Next meeting: Online, Jitsi, Tuesday, 2026-01-06 20:00
Check to whom you are replying
Meetings, mailing list, IRC, ... https://dorset.lug.org.uk
New thread, don't hijack: mailto:[email protected]
