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)
Mon, Sep 28, 6:13 PM
Unknown Object (File)
Mon, Sep 28, 4:40 PM
Unknown Object (File)
Fri, Sep 11, 4:28 AM
Unknown Object (File)
Thu, Sep 10, 1:55 PM
Unknown Object (File)
Wed, Sep 9, 12:19 AM
Unknown Object (File)
Sat, Sep 5, 8:48 PM
Unknown Object (File)
Sep 5 2026, 8:43 AM
Unknown Object (File)
Sep 4 2026, 4:30 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.