src/usr.bin/limits, branch stable/14 FreeBSD source tree limits: Fix pipebuf resource type 2026-06-08T23:00:53+00:00 Dag-Erling Smørgrav des@FreeBSD.org 2026-06-04T22:41:41+00:00 d6800be31a1e1e51f8fa34dfb0654402f323d109 * pipebuf is a size but is listed as a count PR: 295623 MFC after: 1 week Fixes: f54f41403d14 ("usr.bin/limits: support RLIMIT_PIPEBUF") Reviewed by: kib Differential Revision: https://reviews.freebsd.org/D57456 (cherry picked from commit ad524568f9fb77e270a22744d81b9cea0a2ab0eb) 
* pipebuf is a size but is listed as a count

PR:		295623
MFC after:	1 week
Fixes:		f54f41403d14 ("usr.bin/limits: support RLIMIT_PIPEBUF")
Reviewed by:	kib
Differential Revision:	https://reviews.freebsd.org/D57456

(cherry picked from commit ad524568f9fb77e270a22744d81b9cea0a2ab0eb)
limits tests: Try to fix spurious cputime test failures 2025-03-07T22:51:48+00:00 Mark Johnston markj@FreeBSD.org 2025-02-14T16:26:19+00:00 0599d2a1c5996cef4d79a3fbe753d863cdd2359b I very occasionally see test failures caused by the total CPU time being several milliseconds under 3s. The test runs "limits -t 3 time <busy loop>" and verifies that the reported time elapsed is at least 3s (and not too much more). In particular, any time spent executing time(1) itself is counted against the limit but not recorded in the output. I think it makes more sense to reverse the order, so that the CPU time limit is not applied to time(1) itself. This also resolves the test failures I was seeing, which were reproducible only under load (i.e., running many tests in parallel). MFC after: 2 weeks Sponsored by: Klara, Inc. (cherry picked from commit 0f63c4af5e4761680550b0aa08cc96f52076c08c) 
I very occasionally see test failures caused by the total CPU time being
several milliseconds under 3s.  The test runs "limits -t 3 time <busy
loop>" and verifies that the reported time elapsed is at least 3s (and
not too much more).  In particular, any time spent executing time(1)
itself is counted against the limit but not recorded in the output.

I think it makes more sense to reverse the order, so that the CPU time
limit is not applied to time(1) itself.  This also resolves the test
failures I was seeing, which were reproducible only under load (i.e.,
running many tests in parallel).

MFC after:	2 weeks
Sponsored by:	Klara, Inc.

(cherry picked from commit 0f63c4af5e4761680550b0aa08cc96f52076c08c)
usr.bin/limits: support RLIMIT_PIPEBUF 2024-10-05T07:08:54+00:00 Konstantin Belousov kib@FreeBSD.org 2024-09-10T04:13:46+00:00 25902860b2707ab840543eadb3d4e6bcdd8fee01 (cherry picked from commit f54f41403d149e867b896ae753a0e7e2b0c738b0) 
(cherry picked from commit f54f41403d149e867b896ae753a0e7e2b0c738b0)
Remove $FreeBSD$: two-line nroff pattern 2023-08-16T17:55:10+00:00 Warner Losh imp@FreeBSD.org 2023-08-16T17:55:10+00:00 fa9896e082a1046ff4fbc75fcba4d18d1f2efc19 Remove /^\.\\"\n\.\\"\s*\$FreeBSD\$$\n/ 
Remove /^\.\\"\n\.\\"\s*\$FreeBSD\$$\n/
Remove $FreeBSD$: one-line sh pattern 2023-08-16T17:55:03+00:00 Warner Losh imp@FreeBSD.org 2023-08-16T17:55:03+00:00 d0b2dbfa0ecf2bbc9709efc5e20baf8e4b44bbbf Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/ 
Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/
Remove $FreeBSD$: one-line .c pattern 2023-08-16T17:54:42+00:00 Warner Losh imp@FreeBSD.org 2023-08-16T17:54:42+00:00 1d386b48a555f61cb7325543adbbb5c3f3407a66 Remove /^[\s*]*__FBSDID\("\$FreeBSD\$"\);?\s*\n/ 
Remove /^[\s*]*__FBSDID\("\$FreeBSD\$"\);?\s*\n/
Mark usage function as __dead2 in programs where it does not return 2023-07-07T16:45:18+00:00 Alfonso Gregory gfunni234@gmail.com 2023-07-07T16:39:23+00:00 a1b6427a97879ee0034797b2c75ecd107312456a In most cases, usage does not return, so mark them as __dead2. For the cases where they do return, they have not been marked __dead2. Reviewed by: imp Pull Request: https://github.com/freebsd/freebsd-src/pull/735 
In most cases, usage does not return, so mark them as __dead2. For the
cases where they do return, they have not been marked __dead2.

Reviewed by: imp
Pull Request: https://github.com/freebsd/freebsd-src/pull/735
Update/fix Makefile.depend for userland 2023-04-19T00:14:23+00:00 Simon J. Gerraty sjg@FreeBSD.org 2023-04-19T00:14:23+00:00 d9a42747950146bf03cda7f6e25d219253f8a57a 






limits_test: validate CPU time used, not real time
2023-04-14T21:16:05+00:00

Eric van Gyzen
vangyzen@FreeBSD.org

2023-04-14T21:11:29+00:00

485f783f882ed026cdbfede89aa7bddad3fffdf3

RLIMIT_CPU applies to CPU time, not real (wall-clock) time.
This test failed in AWS, where the real time was 5-7 seconds.

Sum the user and system CPU time used, and validate that.

While I'm here, don't bother specifying -s exit:0 or -e empty,
since those are checked by default.

MFC after:	1 week
Sponsored by:	Dell EMC Isilon





RLIMIT_CPU applies to CPU time, not real (wall-clock) time.
This test failed in AWS, where the real time was 5-7 seconds.

Sum the user and system CPU time used, and validate that.

While I'm here, don't bother specifying -s exit:0 or -e empty,
since those are checked by default.

MFC after:	1 week
Sponsored by:	Dell EMC Isilon







pkgbase: Put more binaries/lib in runtime
2021-12-21T09:17:27+00:00

Emmanuel Vadot
manu@FreeBSD.org

2021-12-14T14:31:30+00:00

93c43690960274dd3bb67b1ee0f1dd3ca4d13def

Move some needed binaries/libs from FreeBSD-utilities to FreeBSD_runtime.
This is everything needed to boot to multiuser with FreeBSD-rc installed.

MFC after:	2 weeks
Sponsored by:	Beckhoff Automation GmbH & Co. KG
Differential Revision:	https://reviews.freebsd.org/D33435





Move some needed binaries/libs from FreeBSD-utilities to FreeBSD_runtime.
This is everything needed to boot to multiuser with FreeBSD-rc installed.

MFC after:	2 weeks
Sponsored by:	Beckhoff Automation GmbH & Co. KG
Differential Revision:	https://reviews.freebsd.org/D33435