Page MenuHomeFreeBSD

libcasper.3: document cap_init's single-threaded program requirement
ClosedPublic

Authored by asomers on Jan 10 2023, 7:03 PM.
Tags
None
Referenced Files
F148085262: D38020.id.diff
Sun, Mar 15, 4:12 PM
F148038609: D38020.id.diff
Sun, Mar 15, 8:29 AM
Unknown Object (File)
Sat, Mar 14, 8:58 PM
Unknown Object (File)
Sat, Mar 14, 7:06 PM
Unknown Object (File)
Fri, Feb 27, 8:31 PM
Unknown Object (File)
Fri, Feb 27, 10:03 AM
Unknown Object (File)
Feb 8 2026, 10:09 AM
Unknown Object (File)
Feb 8 2026, 6:15 AM
Subscribers

Details

Summary

Because it internally forks.

[skip ci]
MFC after: 1 week
Sponsored by: Axcient

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

imp added inline comments.
lib/libcasper/libcasper/libcasper.3
99

Currently single threaded programs, or programs that haven't yet started additional threads? I suppose the former is more correct, but maybe the latter is easier to follow?

But just a suggestion... If you don't like it, I'm good with what's here.

This revision is now accepted and ready to land.Jan 10 2023, 7:06 PM
emaste added inline comments.
lib/libcasper/libcasper/libcasper.3
99

"currently" reads somewhat strangely to me too. Maybe something like "in a single-threaded context" or "before additional threads (if any) are started"?

In any case like @imp I think it's better to have something here so up to you.

lib/libcasper/libcasper/libcasper.3
99

"single-threaded context" sounds nice. I'll use that one.