On Fri, Jun 18, 2021 at 04:27:36PM -0500, Scott Cheloha wrote:
>
> I've also added a CAVEATS section.
>
> I've also tweaked the .Nd summary:
>
> .Nd schedule SIGALRM delivery
>
> Thoughts?
>
reads ok to me. one possible tweak inline:
> Index: alarm.3
>
On Fri, 18 Jun 2021 16:27:36 -0500, Scott Cheloha wrote:
> Maybe this?
>
> The
> .Fn alarm
> function schedules the
> .Dv SIGALRM
> signal for delivery to the calling process after the given number of
> .Fa seconds
> have elapsed.
>
> I've also added a CAVEATS section.
>
> I've also tweaked the
On Fri, Jun 18, 2021 at 12:46:38PM -0600, Theo de Raadt wrote:
> Todd C. Miller wrote:
>
> > On Fri, 18 Jun 2021 12:02:18 -0600, "Theo de Raadt" wrote:
> >
> > > But I dislike this text since it doesn't speak to the underlying
> > > mechanism.
> > >
> > > The
> > > .Fn alarm
> > > function
Todd C. Miller wrote:
> On Fri, 18 Jun 2021 12:02:18 -0600, "Theo de Raadt" wrote:
>
> > But I dislike this text since it doesn't speak to the underlying
> > mechanism.
> >
> > The
> > .Fn alarm
> > function configures the process
> > .Va ITIMER_REAL
> > interval timer with
> > .Xr setitimer 2
On Fri, 18 Jun 2021 12:02:18 -0600, "Theo de Raadt" wrote:
> But I dislike this text since it doesn't speak to the underlying
> mechanism.
>
> The
> .Fn alarm
> function configures the process
> .Va ITIMER_REAL
> interval timer with
> .Xr setitimer 2
> to deliver a
> .Va SIGALRM
> signal in the
Scott Cheloha wrote:
> I want to improve the alarm(3) manpage. Here's a first attempt:
>
> - Correct the initial behavior description. alarm(3) does not "wait".
> It schedules signal delivery at a point in the future.
you are right about this.
> The
> .Fn alarm
> +function causes the
Hi,
I want to improve the alarm(3) manpage. Here's a first attempt:
- Correct the initial behavior description. alarm(3) does not "wait".
It schedules signal delivery at a point in the future.
- If alarm(3) is not itself "asserting" the signal we need to specify
who the signal is
