Hi Pádraig,
I wrote:
> > 5) The same thing with 'cp -a' succeeds:
> >
> > $ build-sparc64/src/cp -a /var/tmp/foo3941 $HOME/foo3941; echo $?
> > 0
> > $ build-sparc64-no-acl/src/cp -a /var/tmp/foo3941 $HOME/foo3941; echo $?
> > 0
You wrote:
> The psuedo code that install(1) uses is:
>
>
Hi,
The 'install' program from coreutils-9.5 fails to copy a regular file
from an ext4 mount to an autofs/cifs mount.
The same operation, with 'cp -a', works fine.
Also, it works fine when coreutils was built with the configure options
"--disable-acl --disable-xattr".
How to reproduce
Mon Sep 17 00:00:00 2001
From: Bruno Haible
Date: Sun, 31 Mar 2024 21:31:34 +0200
Subject: [PATCH] canonicalize[-lgpl] tests: Fix test failure on musl libc.
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Reported by Adept's Lab via Pádraig Brady
Andreas Schwab wrote:
> > Yes. And make sure that it has a time zone database installed at all.
>
> Why? That doesn't make any sense.
You can leave the consideration of which test case makes sense or not
on my side.
What we need from you, as a reporter, is a statement on which
platform (distro
Andreas Schwab wrote:
> > FAIL: test-localtime_r
> > ==
> >
> > test-localtime_r.c:58: assertion 'result->tm_hour == 18' failed
> > FAIL test-localtime_r (exit status: 134)
> >
> > FAIL: test-localtime_r-mt
> > =
> >
> > thread2 disturbed by thread1!
Pádraig Brady wrote:
> > I think it is enough to remove the 'long double' part from the test
> > (option letter 'L')...
>
> Pushed that in your name at:
> https://git.sv.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=bec53850b
Thank you. Yes, that's what I meant :-)
I confirm that it fixes the
Pádraig Brady wrote:
> The original bug report was not specific to floats, so I'll just remove them
> from the test.
I think it is enough to remove the 'long double' part from the test
(option letter 'L'). 'float' and 'double' are standardized by IEEE 754
(except on Linux/m68k) and don't have
On two machines (Linux/sparc64 and Linux/riscv64, real hardware, Gentoo)
I see reproducible test failures of tail/retry. See attached log files.
I do *not* see these failures with architectures in the same farm (matoro.tk).
I also do *not* see these failures in QEMU VMs with a local (surely ext4)
Pádraig Brady wrote:
> A documentation patch would be very useful.
> If you search for "Decorate Sort Undecorate" in coreutils.texi
> you can see an existing example of this DSU pattern.
> I would also mention DSU if adding another example.
OK, I'll provide doc input for this (post 9.5).
> Re
Pádraig Brady wrote:
> OK done. Please use coreutils-9.4.185-541b02.tar.xz
Thanks. With this, all tests pass on CentOS 8 Stream.
Pádraig Brady wrote:
> We plan to release coreutils-9.5 in the next few days
I would suggest to update to the current gnulib, in order to get these
two fixes:
https://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commit;h=3978cc5adb34f3152f119d46f53e6e8e107158fa
Pádraig Brady wrote:
> >>> The misc/numfmt test fails on
> >>> - Alpine Linux 3.18,
> >>> - macOS 12.5,
> >>> - FreeBSD 14.0,
> >>> - Solaris 11 OpenIndiana.
> >>>
> >>> Find attached the test-suite.log files.
> >>> ...
> FreeBSD 14 at least looks to be counting bytes rather than
I wrote:
> The help/help-version test fails on AIX 7.1 and AIX 7.3.1.
>
> test-suite.log on AIX 7.1:
>
>
> FAIL: tests/help/help-version
> =
>
> env: '[': No such file or directory
> env: '[': No such file or directory
> env: '[': No such file or directory
> FAIL: [
Pádraig Brady wrote:
> > The misc/numfmt test fails on
> >- Alpine Linux 3.18,
> >- macOS 12.5,
> >- FreeBSD 14.0,
> >- Solaris 11 OpenIndiana.
> >
> > Find attached the test-suite.log files.
> >
> > If these test failures are due to platform-specific *printf bugs, please
> >
I confirm: this unit test now passes on all mentioned platforms.
Pádraig Brady wrote:
> > The mv/mv-exchange test fails on:
> >- NetBSD 9.3
> >- OpenBSD 7.4
> >- AIX 7.1
> >- AIX 7.3.1
>
> The attached should fix the issue with this new test.
I confirm: It fixes the test failure on all 4 platforms.
Pádraig Brady wrote:
> > The ls/removed-directory test fails on FreeBSD 14.0.
> >
> > tests-suite.log from FreeBSD 14.0:
> >
> >
> > FAIL: tests/ls/removed-directory
> >
> >
> > diff -u /dev/null err
> > --- /dev/null 1970-01-01
> > +++ err 1970-01-01
Pádraig Brady wrote:
> > The ls/dired test fails on:
> >- FreeBSD 14.0,
> >- Solaris 11 OpenIndiana.
>
> https://github.com/coreutils/coreutils/commit/a51af4329
Thanks. I confirm that it fixes the test failure on both platforms.
Pádraig Brady wrote:
> The attached fixes this by including the setgid bit
> in the fallback mode if appropriate.
Thanks. I confirm that it fixes the test failure.
Pádraig Brady wrote:
> I'll apply the attached anyway which should avoid this issue.
Thanks. I confirm that it fixes the failure.
The documentation of 'uniq' [1] says:
"The input need not be sorted, but repeated input lines are
detected only if they are adjacent. If you want to discard
non-adjacent duplicate lines, perhaps you want to use 'sort -u'."
When I wrote gnulib-tool many years ago, as a shell script, I
Pádraig Brady wrote:
> > You should also have access to cfarm215.cfarm.net and cfarm216.cfarm.net
> > (just announced today).
>
> Nice machines.
> Though I can't repo there, I'm guessing because they've
> both multi and uni byte fr locales installed.
I had seen the issue on Solaris 11
Pádraig Brady wrote:
> while uniq (c32isblank) now determines
> it is not blank (which seems more correct).
I agree that U+00A0 NO-BREAK SPACE should better be considered to be non-blank
(and Gnulib's c32isblank does so).
> The only solaris 11 system I have access to, only has the fr_FR.UTF-8
On AIX 7.3, I also see three other test failures:
- misc/stdbuf
- install/basic-1
- mkdir/p-3
Here's the test-suite.log.
FAIL: tests/misc/stdbuf
===
stdbuf: invalid mode 'l'
stdbuf: invalid mode '18446744073709551616': Value too large to be stored in
data type
The misc/numfmt test fails on
- Alpine Linux 3.18,
- macOS 12.5,
- FreeBSD 14.0,
- Solaris 11 OpenIndiana.
Find attached the test-suite.log files.
If these test failures are due to platform-specific *printf bugs, please
provide a test case for *printf at the C level. Then I can add a
The chmod/symlinks test fails on:
- Alpine Linux 3.18,
- macOS 12.5,
- FreeBSD 14.0,
- NetBSD 9.3 and 10.0-rc4,
- OpenBSD 7.4,
- Solaris 11.4,
- AIX 7.1 and 7.3.1.
Find attached the test-suite.log files.
FAIL: tests/chmod/symlinks
==
+
The cp/preserve-mode test fails on Alpine Linux 3.18.
test-suite.log from Alpine Linux 3.18:
FAIL: tests/cp/preserve-mode
+ initial_cwd_=/home/bruno/coreutils-9.4.170-7b206/build
+ testdir_prefix_
+ printf gt
+ pfx_=gt
+ mktempd_
The chown/preserve-root test fails on macOS 12.5.
test-suite.log from macOS 12.5:
FAIL: tests/chown/preserve-root
===
++ initial_cwd_=/Users/haible/STORAGE/coreutils-9.4.170-7b206/build
+++ testdir_prefix_
+++ printf gt
++ pfx_=gt
+++ mktempd_
The ls/dired test fails on:
- FreeBSD 14.0,
- Solaris 11 OpenIndiana.
test-suite.log on FreeBSD 14.0:
FAIL: tests/ls/dired
tail: cannot open '+53' for reading: No such file or directory
Mismatch! Expected: 1a, Found:
tail: cannot open '+98' for reading: No such file
The ls/removed-directory test fails on FreeBSD 14.0.
tests-suite.log from FreeBSD 14.0:
FAIL: tests/ls/removed-directory
diff -u /dev/null err
--- /dev/null 1970-01-01
+++ err 1970-01-01
+ls: reading directory '.': No such file or directory
FAIL
The date/date-debug, date/date-tz tests fail on NetBSD 9.3 and 10.0-rc4.
test-suite.log from NetBSD 9.3:
FAIL: tests/date/date-debug
===
--- exp22024-03-24 12:44:31.942851024 +0100
+++ out22024-03-24 12:44:31.947773870 +0100
@@ -5,9 +5,8 @@
date: error:
The mv/mv-exchange test fails on:
- NetBSD 9.3
- OpenBSD 7.4
- AIX 7.1
- AIX 7.3.1
test-suite.log from NetBSD 9.3:
FAIL: tests/mv/mv-exchange
==
mv: cannot exchange 'a' and 'b': Not supported
FAIL tests/mv/mv-exchange.sh (exit status: 1)
test-suite.log from
The tail/pipe-f2 test fails on NetBSD 9.3 and 10.0-rc4.
test-suite.log on NetBSD 9.3:
FAIL: tests/tail/pipe-f2
--- exp 2024-03-24 12:45:54.627129684 +0100
+++ out 2024-03-24 12:45:54.628038908 +0100
@@ -1 +0,0 @@
-1
kill: 20415: No such process
FAIL
The stty/stty-row-col test fails on Solaris 11.4.
test-suite.log on Solaris 11.4:
FAIL: tests/stty/stty-row-col
=
++ initial_cwd_=/export/home/bruno/coreutils-9.4.170-7b206/build-64
+++ testdir_prefix_
+++ printf gt
++ pfx_=gt
+++ mktempd_
The uniq/uniq test fails on Solaris 11 OpenIndiana.
test-suite.log on Solaris 11 OpenIndiana:
FAIL: tests/uniq/uniq
=
uniq (GNU coreutils) 9.4.170-7b206
Copyright (C) 2024 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
The help/help-version test fails on AIX 7.1 and AIX 7.3.1.
test-suite.log on AIX 7.1:
FAIL: tests/help/help-version
=
env: '[': No such file or directory
env: '[': No such file or directory
env: '[': No such file or directory
FAIL: [
0+1 records in
0+1 records out
On the machine gcc119.fsffrance.org (AIX 7.3.1), with gcc
(CC="/opt/freeware/bin/gcc -maix64"), there is a compilation error:
CC lib/libcoreutils_a-md5-stream.o
In file included from /usr/include/openssl/opensslv.h:125,
from ../lib/md5.h:36,
from
Hi,
Building coreutils-9.4.170-7b206 on a glibc system, with clang and ASAN and
UBSAN options, produces 4 test failures.
I'm using clang 17.0.4 with the options
CC="$CC
-fsanitize=address,undefined,signed-integer-overflow,shift,integer-divide-by-zero"
CFLAGS="-O0 -fno-omit-frame-pointer -ggdb"
Pádraig Brady wrote:
> > Does this work for all the various names of libcrypto in various distros?
> >
> > Debian 12 libcrypto.so.3
> > Ubuntu 22.04libcrypto.so.1.1 libcrypto.so.3
> > Slackware 15libcrypto.so.1.1
> > openSUSE 15.5 libcrypto.so.1.1
> > CentOS Stream 9
Paul Eggert wrote:
> Thanks for the patch. I was hoping that we didn't need to worry about
> older platforms needing -ldl. Oh well.
Distros with glibc < 2.34 include:
Debian 11
CentOS 8 stream
Fedora 34
openSUSE 15.5
Slackware 15
These are not obsolete, so far.
> The patch causes
l.so.2
/lib64/ld-linux-x86-64.so.2
and with the patch, 'sort' loads the libraries
linux-vdso.so.1
libdl.so.2
libpthread.so.0
libc.so.6
/lib64/ld-linux-x86-64.so.2
— that is, libdl.so.2 is getting loaded anyway.
>From c30a0e55c95e0ae7062ee2ececf85cd0dbfe49fb Mon Sep 17 00:00:00 20
001
From: Bruno Haible
Date: Mon, 26 Feb 2024 22:33:18 +0100
Subject: [PATCH] join: Avoid test failure on systems which have no French
UTF-8 locale
* tests/misc/join-utf8.sh: Test the value of LOCALE_FR_UTF8 against
'none', not against a missing value.
---
tests/misc/join-utf8.sh | 2 +-
1 f
Pádraig Brady wrote:
> >> + void *handle = dlopen ("libcrypto.so", RTLD_LAZY | RTLD_GLOBAL);
> >
> > That only works if libopenssl-devel is installed.
>
> Good spot.
> I'd already pushed a fix for this at:
> https://git.sv.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=3bbdb3938
Does this work
> I actually thought something like the CLOCK_MONOTONIC or CLOCK_BOOTTIME were
> used for providing uptime to the user, but those do not allow date changes.
You are assuming a certain implementation, and then thinking what properties
the program "must" have. Try thinking the other way around:
Thorsten Kukuk wrote:
> Who creates an additional line for "seat0", which no other tools creates
> and which it did not create before. Since some display manager writes
> wrongly multiple utmp entries
To me, that's a feature, not a bug. Systemd has introduced the concept of
seats [1], and the
[CCing bug-gnulib, because the readutmp code lives in gnulib]
Thorsten Kukuk wrote:
> if there is no /run/utmp file, /usr/bin/who falls back correctly to the
> systemd-logind interface and shows correct data.
>
> But there are applications, which don't use the libc interface for
>
Paul Eggert wrote:
> Yes please. If chmod also does not work coreutils might need more
> workarounds.
>
> Just to be clear; please try it on a file where chmod should fail
> because you don't own the file and you're not root. chmod should fail
> with EPERM in this case; it it fails with EACCES
Paul Eggert wrote:
> Good, thanks for confirming that the chmod family does not have a
> similar bug.
Well, you asked me to try it on / but / is an ext4 FS, not a CIFS FS
on my system. Should I try it also on a directory inside the CIFS mount?
> I installed the attached workaround into
Paul Eggert wrote:
> > If you compile and run the attached
> > program on a file that you don't own (e.g., './a.out /'), does it
> > incorrectly issue "Permission denied" instead of "Operation not
> > permitted" diagnostics?
and I replied:
> In this case, the diagnostic is "Operation not
Paul Eggert wrote:
> If you compile and run the attached
> program on a file that you don't own (e.g., './a.out /'), does it
> incorrectly issue "Permission denied" instead of "Operation not
> permitted" diagnostics?
In this case, the diagnostic is "Operation not permitted" (from EPERM):
$
Paul Eggert wrote:
> it'd be helpful to know whether the bug is limited to fchownat or
> (as I suspect) applies also to the other chown variants. Could you try
> running the attached program on your platform, to see whether the bug
> affects these other variants?
It applies to all 4 variants,
ils/2023-08/msg00096.html
[2] https://en.wikipedia.org/wiki/OpenSSL#Major_version_releases
2023-09-01 Bruno Haible
crypto/{sha*,md5,sm3}-buffer: Fix --with-openssl (regr. 2023-08-26).
Reported by Agostino Sarubbo via Sam James in
<https://lists.gnu.org/archive/html/b
ssions).
This patch fixes it.
2023-08-31 Bruno Haible
readutmp: Fix memory leak introduced by last commit.
* lib/readutmp.c (read_utmp_from_systemd): If num_sessions == 0 and
sessions != NULL, do call free (sessions).
diff --git a/lib/readutmp.c b/lib/readutmp.c
index e991
Thanks for looking into this, Paul.
But there's a big misunderstanding. This is not on Android. It's on
Linux with glibc (Ubuntu 22.04, to be precise), as can be seen from the
log file:
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
and from the fact that I could
When I move a directory from an ext4 file system to a CIFS v1 file system,
I get a diagnostic
mv: failed to preserve ownership for '...': Permission denied
although the owner and group of the directory after and before the move
are the same. So, there is actually nothing to warn about.
$ mv
Pádraig Brady wrote:
> I don't think there is anything blocking here anyway.
> I'll prepare the release...
It's your decision. But I happen to agree :)
Bruno
Pádraig Brady wrote:
> A lot of the test failures are just because
> curly quotes are being used in diagnostics,
> thus causing expected messages not to match.
> Searching for curly quotes in the logs show many instances like:
>
>-sort: text ordering performed using simple byte comparison
>
Description: application/gzip
From 31c7d3ae272d54badba9f432db5068d52c26dda1 Mon Sep 17 00:00:00 2001
From: Bruno Haible
Date: Mon, 28 Aug 2023 12:07:18 +0200
Subject: [PATCH] maint: Avoid test failure on Android
* gl/tests/test-mbsalign.c (main): Skip the unibyte truncation test
on Android, when
Pádraig Brady wrote:
> Weird. I guess the `: > missing\dir` construct causes the script
> to exit early in failure. Perhaps `if touch missing\dir` would work better.
No, that does not make a difference. Both ": > 'missing\dir'" and
"touch 'missing\dir'" succeed when 'missing' is an existing
Pádraig Brady wrote:
> > Here is a comparison of the failing tests:
> >
> > === Cygwin 2.9.0 Cygwin 3.4.6 ===
> > FAIL: tests/rm/cycleFAIL: tests/rm/cycle
> > FAIL: tests/chmod/no-x FAIL: tests/chmod/no-x
> > FAIL:
Pádraig Brady wrote:
> The cksum failures are regressions,
> which should be handled by the two attached patches.
After applying these two patches, only the 'FAIL: tests/cksum/b2sum' is gone.
The 'FAIL: tests/cksum/md5sum-bsd' is still there. Find attached the new log
file.
> On Cygwin 2.9.0/x86_64, I see 8 ERROR and 30 FAIL:
Whereas on Cygwin 3.4.6/x86_64, I see 8 ERROR and 29 FAIL:
ERROR: tests/tail/inotify-hash-abuse
ERROR: tests/rm/rm-readdir-fail
ERROR: tests/cp/nfs-removal-race
ERROR: tests/df/no-mtab-status
ERROR: tests/df/skip-duplicates
ERROR:
The build succeeds and all tests pass on the following platforms:
Linux
Guix 1.4
Ubuntu 22.04
Ubuntu 22.04 / 32
Ubuntu 22.04 / x32
Debian 9.1
Debian 11.1
Debian 12 / powerpc64
CentOS 8-stream
CentOS Stream 9
Fedora 28 / riscv64
Fedora Rawhide Cinnamon
OpenSUSE Leap 15.2
Pádraig Brady wrote:
> Perhaps fpurge() is needed on FreeBSD to avoid the repeated warning?
> I don't have easy access to a FreeBSD machine at present,
> to test this change:
>
> diff --git a/src/head.c b/src/head.c
> index 7bba1420c..da32c886f 100644
> --- a/src/head.c
> +++ b/src/head.c
> @@
On the Hurd, I got weird results during "make check"; see attached
screenshot.
Thus I restarted from a clean Hurd environment, and now the
"make check" run terminated reasonably, with 18 FAILures.
Find attached the log file.
hurd-test-suite.log.gz
Description: application/gzip
Pádraig Brady wrote:
> Perhaps 'sleep' is a shell builtin here which is confusing things?
Yes:
$ type sleep
sleep is a shell builtin
> Does the following help (I don't have easy access to an alpine system):
> diff --git a/tests/misc/usage_vs_getopt.sh b/tests/misc/usage_vs_getopt.sh
> index
On NetBSD 9.3/x86_64, I see 3 test failures:
FAIL: tests/date/date-debug
FAIL: tests/date/date-tz
FAIL: tests/tail/pipe-f2
On NetBSD 8.0/sparc64, I see these test failures, and additionally:
FAIL: tests/touch/not-owner
This is a subset of what I reported in
On Solaris 11.4, in 64-bit mode, I still get 1 failure:
FAIL: tests/stty/stty-row-col
like already reported in
https://lists.gnu.org/archive/html/coreutils/2023-03/msg00035.html
The log file is attached.
solaris114-test-suite.log.gz
Description: application/gzip
There are no test failures on
- FreeBSD 12.0/x86_64
- FreeBSD 12.2/arm64
- FreeBSD 13.0/x86_64, FreeBSD 13.0/arm64
However:
* There is 1 test failure on FreeBSD 13.1/x86_64:
FAIL: tests/head/head-write-error
Same as my earlier report in
On Alpine Linux 3.18 (x86), I see two test failures:
FAIL: tests/misc/usage_vs_getopt
FAIL: tests/cp/preserve-mode
The first one is new.
The second one I already reported in
https://lists.gnu.org/archive/html/coreutils/2023-03/msg00034.html
and you analyzed it in
On CentOS 5 (64-bit mode), I see 4 test failures:
FAIL: tests/sort/sort-continue
FAIL: tests/sort/sort-merge-fdlimit
FAIL: tests/cp/attr-existing
FAIL: tests/mv/part-symlink
Find attached the log file.
centos5-test-suite.log.gz
Description: application/gzip
rom: Bruno Haible
Date: Sun, 27 Aug 2023 01:10:13 +0200
Subject: [PATCH] maint: Fix link errors of sort, split on CentOS 5 and Solaris
10
* src/local.mk (src_sort_LDADD, src_split_LDADD): Add $(CLOCK_TIME_LIB).
---
src/local.mk | 2 ++
1 file changed, 2 insertions(+)
diff --git a/src/local.m
On AIX 7.3.1, after fixing the compilation errors
https://lists.gnu.org/archive/html/bug-gnulib/2023-08/msg00179.html
https://lists.gnu.org/archive/html/coreutils/2023-08/msg00062.html
there are test failures. I did 3 builds:
- 64-bit with gcc
- 64-bit with ibm-clang
- 32-bit with ibm-clang
Pádraig Brady wrote:
> The fact that ',' isn't used as the decimal point is surprising,
> and is what's causing the test to fail.
Ah, I see. Yes, for some tests one only needs a fr_FR.UTF-8 that supports
UTF-8 in LC_CTYPE, whereas for other tests it also needs to support the
LC_NUMERIC category
Paul Eggert wrote:
> Thanks for the further comments. I installed your patch, along with the
> attached additional patches.
The other patch I mentioned, from
https://lists.gnu.org/archive/html/coreutils/2023-08/msg00028.html ,
is also needed, for the "VM saved/sleep" change on NetBSD, OpenBSD,
Hi,
Doing "make check" of current coreutils on Alpine Linux 3.18, I see a
test failure that I didn't see with the coreutils-9.3 release:
FAIL: tests/sort/sort-debug-keys
I'm attaching the relevant part of tests/test-suite.log.
Bruno
==
I wrote:
> > I'll provide a NEWS
> > entry afterwards, that summarizes the changes in coreutils + gnulib on the
> > various platforms.
>
Paul Eggert wrote:
> Thanks, this looks good. A NEWS entry would be welcome.
Actually, it's 4 entries:
* The 'uptime' program is now being built on FreeBSD,
rom 2046827462094dde4ac8391865a3edc74e313126 Mon Sep 17 00:00:00 2001
From: Bruno Haible
Date: Mon, 14 Aug 2023 20:59:41 +0200
Subject: [PATCH] maint: Fix compilation error on GNU/Hurd (regression
2023-06-29)
* src/copy.c (set_author): Revert change from MACH_PORT_NULL to
MACH_PORT_nullptr.
---
src/cop
: implicit declaration of function ‘__builtin_cpu_supports’
[-Wimplicit-function-declaration]
The attached patch fixes it.
>From a57d40e3f6997845ce88be6f40813b1b26cb6e16 Mon Sep 17 00:00:00 2001
From: Bruno Haible
Date: Mon, 14 Aug 2023 01:45:39 +0200
Subject: [PATCH] cksum,wc: Fix link er
PS: I wrote:
> (print_uptime): Don't read /proc/uptime
You might wonder: What is the replacement? Namely, as a fallback (for
situations where the current process is running inside a container or jail):
- On Linux, the auxiliary function get_linux_boot_time_final_fallback
reads the info from
ine CLOCK_BOOTTIME 7
I also verified this on a laptop.
>From ff6e92f38b560ade54df4c94e9d91657f740bb4b Mon Sep 17 00:00:00 2001
From: Bruno Haible
Date: Sun, 13 Aug 2023 00:57:23 +0200
Subject: [PATCH] uptime: Include VM sleep time in the "up" duration
* src/uptime.c: Don't in
p 17 00:00:00 2001
From: Bruno Haible
Date: Sat, 12 Aug 2023 23:08:58 +0200
Subject: [PATCH] uptime: Simplify following gnulib changes
* gnulib: Update to newest.
* src/uptime.c: Don't include , .
(print_uptime): Don't call sysctl, get_system_info, as Gnulib's readutmp
module now does this
r
/var/lib/systemd/timers/stamp-apt-daily-upgrade.timer
/var/lib/apt/daily_lock
But I suspect that they may be touched at other moments than during boot.
Therefore here, the workaround with the file time stamps does not work.
But another workaround works:
2023-08-10 Bruno Haible
r
Po Lu wrote:
> >> Both clock_gettime (CLOCK_BOOTIME, ... sysinfo fail with AVC denial
> >> errors and errno set to EACCESS.
> >
> > Was this inside Termux, or inside the Emacs app?
>
> Inside the Emacs app.
Emacs does not have the following in AndroidManifest.xml, which Termux has:
Thorsten Kukuk wrote:
> Not sure how relevant this code still is, but currently I get with this:
>
> lib/readutmp.c: In function 'get_boot_time_uncached':
> lib/readutmp.c:326:35: error: declaration of 'up' shadows a previous local
> [-Werror=shadow]
> 326 | struct timespec
Po Lu wrote:
> Both clock_gettime (CLOCK_BOOTIME, ... sysinfo fail with AVC denial
> errors and errno set to EACCESS.
Was this inside Termux, or inside the Emacs app?
Bruno
the
boot time. Thus it is worth using now.
Find attached a patch.
Bruno
>From bb38f6e5cc9fbf600f698866e268cdcfba636ea6 Mon Sep 17 00:00:00 2001
From: Bruno Haible
Date: Thu, 10 Aug 2023 13:50:57 +0200
Subject: [PATCH] pinky,users,who: Optimize read_utmp invocation
When we are only interes
it depends not only on the Android version and device,
but also on the permissions required by the app?
Bruno
From 9db6a91083ecca9c49bd5353c7624c6388f332fb Mon Sep 17 00:00:00 2001
From: Bruno Haible
Date: Thu, 10 Aug 2023 07:59:19 +0200
Subject: [PATCH] readutmp: Return a boot time also on Android.
*
Po Lu wrote:
> > Also, I don't know how Android records boot time so I'll cc this to Po
> > Lu, the main developer for Emacs on Android.
>
> The boot time is off limits to user programs on Android, for security
> reasons.
No, it isn't. The attached file, when compiled and run under Termux (which
Paul Eggert wrote:
> This patch does not address the problem for Alpine, nor I suspect for
> Android. I suppose Alpine could use the timestamp of /var/run/utmp (or
> is that /run/utmp?) but I don't know how 'configure' would reliably
> detect it's being built or cross-built for Alpine. I'll cc
ebian 9, Ubuntu 17.10, Arch 19.11,
Manjaro 17)
/var/run/utmp (seen on distros with OpenRC, e.g. Alpine Linux)
/var/lib/random-seed (seen on OpenSUSE 12.1, CentOS 5)
And, while at it, also on OpenBSD. It touches /var/db/host.random and
/var/run/utmp.
More info about this problem: I wrote
> I have a VM running in VirtualBox, that I booted 6 days ago, then "saved"
> it (i.e. all the state gets frozen) and resumed it today around 20:30 UTC.
> ...
> So, both programs show a "boot time" that is just 5 hours ago, at a moment
> when
> the VM was in
Thorsten Kukuk wrote:
> > What API do you suggest we use instead?
>
> For me clock_gettime works very well:
> https://github.com/thkukuk/utmpx/blob/main/utmp-to-logind.md#determine-boot-time
Now that I've implemented this method in gnulib's 'readutmp' module
and built coreutils with that, I see
I wrote:
> > (2) The readutmp module should use a runtime 'if' rather than a
> > compile-time
> > #if, in order to dispatch between the systemd backend and the
> > file-based
> > backend.
This patch implements it.
2023-08-08 Bruno H
e approach only has a resolution of 1 µsec. Thanks for the
suggestion.
2023-08-08 Bruno Haible
readutmp: Get the boot time with higher precision.
Suggested by Thorsten Kukuk in
<https://github.com/thkukuk/utmpx/blob/main/utmp-to-logind.md#determine-boot-ti
001-maint-Simplify-after-gnulib-changed.patch .
2023-08-08 Bruno Haible
readutmp: Return entries with unbounded strings on all platforms.
Suggested by Paul Eggert in
<https://lists.gnu.org/archive/html/bug-gnulib/2023-07/msg00165.html>.
* m4/readutmp.m4
Robert Pluim wrote:
> Thorsten> They don't record at all.
> Thorsten> Which means tools like who just don't show anything. And emacs
> will
> Thorsten> never find out the boot time with the current code.
>
> What API do you suggest we use instead?
musl libc runs only on Linux. On
gllib/readutmp.c", line 76.20: 1506-022 (S) "ut_ts" is not a member of
"const struct utmp".
make: 1254-004 The error code from the last command is 1.
On Android:
../../gllib/readutmp.c:76:20: error: no member named 'ut_ts' in 'struct utmp';
did you mean 'ut_tv'?
This patc
rror: no member named 'ut_id' in 'struct utmp'
enum { UT_ID_SIZE = sizeof (((STRUCT_UTMP *) 0)->ut_id) };
~~~ ^
This patch fixes it.
2023-08-08 Bruno Haible
readutmp: Fix compilation error on OpenBSD (regr. 2023-08-02).
Thorsten Kukuk wrote:
> On musl libc systems like Alpine,
> you don't have utmp nor wtmp.
But on Alpine Linux, I don't see a systemd nor a logind daemon.
How are logins meant to be recorded on this system?
Bruno
1 - 100 of 583 matches
Mail list logo
