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)
Thu, Oct 16, 6:04 PM
Unknown Object (File)
Thu, Oct 16, 5:30 PM
Unknown Object (File)
Wed, Oct 15, 2:47 AM
Unknown Object (File)
Sun, Oct 12, 2:16 AM
Unknown Object (File)
Mon, Oct 6, 1:24 AM
Unknown Object (File)
Sat, Sep 20, 1:11 AM
Unknown Object (File)
Sep 10 2025, 7:44 PM
Unknown Object (File)
Sep 6 2025, 2:09 PM
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.