Hi, On Wed, Apr 03, 2024 at 05:06:45PM GMT, наб wrote: > This comes from a real user complaint. sigwait(3) is the most obvious > of the family, and it doesn't mention any of the usage details. > Most of these can be crosslinked, but not mentioning the sigprocmask(2) > requirement is malice. > > Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@xxxxxxxxxxxxxxxxxx> > --- > man3/sigwait.3 | 6 +++++- > 1 file changed, 5 insertions(+), 1 deletion(-) > > diff --git a/man3/sigwait.3 b/man3/sigwait.3 > index 226a97e6f..b65cd4db3 100644 > --- a/man3/sigwait.3 > +++ b/man3/sigwait.3 > @@ -36,6 +36,8 @@ .SH DESCRIPTION > one of the signals specified in the signal set > .I set > becomes pending. > +For a signal to become pending, it must first be blocked with I added a newline after the comma, and then applied the patch; thanks! Have a lovely day! Alex > +.BR sigprocmask (2). > The function accepts the signal > (removes it from the pending list of signals), > and returns the signal number in > @@ -81,7 +83,9 @@ .SH ATTRIBUTES > .SH VERSIONS > .BR sigwait () > is implemented using > -.BR sigtimedwait (2). > +.BR sigtimedwait (2); > +consult its > +.BR NOTES . > .P > The glibc implementation of > .BR sigwait () > -- > 2.39.2 -- <https://www.alejandro-colomar.es/>
Attachment:
signature.asc
Description: PGP signature
