Date: Tue, 10 Jan 2023 13:55:15 -0500 From: Ed Maste <emaste@freebsd.org> To: Alan Somers <asomers@freebsd.org> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: libcasper and async-signal-safety Message-ID: <CAPyFy2CYwFbUEzb=2OnX%2BNu26F=Km8Y1v56EjqwV1=cwyiOncw@mail.gmail.com> In-Reply-To: <CAOtMX2jwqZHw-3D6rek5dUrAcM4=45n_=a=LVkahdJsOBz8%2B6A@mail.gmail.com> References: <CAOtMX2jwqZHw-3D6rek5dUrAcM4=45n_=a=LVkahdJsOBz8%2B6A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 10 Jan 2023 at 13:45, Alan Somers <asomers@freebsd.org> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2CYwFbUEzb=2OnX%2BNu26F=Km8Y1v56EjqwV1=cwyiOncw>