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
Unknown Object (File)
Fri, Mar 22, 9:15 PM
Unknown Object (File)
Tue, Mar 12, 8:37 PM
Unknown Object (File)
Fri, Mar 8, 7:18 PM
Unknown Object (File)
Fri, Mar 8, 7:37 AM
Unknown Object (File)
Jan 12 2024, 2:58 PM
Unknown Object (File)
Jan 4 2024, 1:14 PM
Unknown Object (File)
Jan 4 2024, 6:02 AM
Unknown Object (File)
Dec 20 2023, 5:48 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 Passed
Unit
No Test Coverage
Build Status
Buildable 49053
Build 45942: arc lint + arc unit

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.