Re: libcasper and async-signal-safety

From: Mariusz Zaborski <>
Date: Wed, 11 Jan 2023 10:12:57 UTC
On Tue, 10 Jan 2023 at 19:55, Ed Maste <> wrote:

> On Tue, 10 Jan 2023 at 13:45, Alan Somers <> wrote:
> >
> > I assume that this is just an oversight.  After all, all of the
> > existing programs in the base system that use casper are
> > single-threaded.  But it's a limitation that ought to be documented in
> > the cap_init(3) man page, right?  Or am I missing something?
> I don't think you're missing anything, and this just needs to be
> explicitly documented. The forking behaviour of Casper services is
> perhaps an internal implementation detail, but the limitations it
> imposes on the consumer should be clear.

I don't think you're missing anything.
Your analysis is correct, I think we just oversight this.