src/bin/timeout, branch main

timeout.1: Document non-POSIX options

2026-04-13T19:52:21Z

MFC after: 3 days Reviewed by: Aaron Li , ziaee Differential Revision: https://reviews.freebsd.org/D56090

timeout: Clean up

2026-02-13T20:19:16Z

* Annotate logv() and fix format string bug. * Don't reinvent str2sig(3). * Reorganize kill_self() so we unblock signals as late as possible, and use raise(2) instead of kill(2). * Explicitly close unused pipe descriptors. * Use correct type to collect result of read(2) and write(2). * Compare return values to 0, not -1. * Sort local variables according to style(9). * Reduce unnecessary nesting. * Reindent. * Fix typo in manual page. MFC after: 1 week Sponsored by: Klara, Inc. Reviewed by: kevans Differential Revision: https://reviews.freebsd.org/D55277

timeout(1): add license header to unit test

2025-09-03T09:52:46Z

Requested by: kevans

timeout(1) tests: atf_fail requires a reason

2025-06-09T23:52:41Z

Reviewed by: markj Sponsored by: The FreeBSD Foundation MFC after: 1 week Differential revision: https://reviews.freebsd.org/D50752

timeout(1): pass full 32bit error return code from the exited child

2025-06-09T23:52:34Z

Switch to use waitid(2) to receive siginfo_t with the complete error code from the exited process. Tested by: pho Reviewed by: markj Sponsored by: The FreeBSD Foundation MFC after: 1 week Differential revision: https://reviews.freebsd.org/D50752

timeout(1): only start the child command after the parent is fully set up

2025-06-09T23:51:19Z

Since the default disposition for SIGCHLD is ignore, the prematurely exited child would cause SIGCHLD dropped. This makes timeout(1) hang, because REAP_STATUS reports a zombie not waited for, but SIGCHLD for it was already lost, so the main loop cannot exit, instead calling into sigsuspend(). Reported and tested by: pho Reviewed by: markj Sponsored by: The FreeBSD Foundation MFC after: 1 week Differential revision: https://reviews.freebsd.org/D50752

timeout(1): print errno when signalling syscalls failed

2025-06-09T23:51:13Z

Tested by: pho Reviewed by: markj Sponsored by: The FreeBSD Foundation MFC after: 1 week Differential revision: https://reviews.freebsd.org/D50752

timeout(1): silence warnings for ESRCH

2025-06-09T23:51:06Z

It is possible for the child to become zombie and then there is nothing to signal. Reported and tested by: pho Reviewed by: markj Sponsored by: The FreeBSD Foundation MFC after: 1 week Differential revision: https://reviews.freebsd.org/D50752

timeout(1): Document the reaper implementation and behaivor

2025-04-16T19:45:38Z

If timeout(1) runs with the --foreground option, it becomes the reaper of the command and its descendants and will wait for all of them to terminate. This behavior is different from the old FreeBSD version and GNU version. For example, if there is a descendant running in the background, like: $ timeout -s INT 2 sh -c 'sleep 4 & sleep 5' when timeout(1) sends the SIGINT to all descendants, the child 'sh' process and the foreground 'sleep 5' process will immediately terminate, but the background 'sleep 4' will be reparented to the timeout(1) itself. Because a background process ignores SIGINT and SIGQUIT, the whole command completes until the background 'sleep 4' finishes. In comparison, the old FreeBSD version and GNU version will just terminate itself, letting the background 'sleep 4' process be reparented to an upper reaper like init. The POSIX.1-2024 standard doesn't specify the required behavior in such cases, so I decided to keep the current implementation. Nonetheless, the updated timeout(1) has changed a lot in order to conform to the standard. Obtained-from: DragonFly BSD

timeout(1): adapt the preserve_status test to the new behaviour

2025-04-16T19:45:38Z

atf-check cannot check anymore the exit number if the program is terminated via a signal, it needs to be catched by -s signal because we cannot pass twice the -s command, we cannot anymore check for the exit value :(