On Sat, 3 Feb 2001, Jamie Lokier wrote:
> Robert H. de Vries wrote:
> > Hi Linus,
> > c. setitimer() can be used only once in a given process, you can have
> >up to 32 (configurable) POSIX timers at the same time in your process.
>
> Why is there a limit? With such a small limit, any
Robert H. de Vries wrote:
> Hi Linus,
> c. setitimer() can be used only once in a given process, you can have
>up to 32 (configurable) POSIX timers at the same time in your process.
Why is there a limit? With such a small limit, any library that wants
to use its own private timers is going
Hi Linus,
Please accept this patch for inclusion. The impact on the kernel is
negligible and it makes the kernel a bit more POSIX feature complete. I
have received good feedback from people who have used the patch and I have
used it a lot myself without any problems.
This patch should not
Hi Linus,
Please accept this patch for inclusion. The impact on the kernel is
negligible and it makes the kernel a bit more POSIX feature complete. I
have received good feedback from people who have used the patch and I have
used it a lot myself without any problems.
This patch should not
Robert H. de Vries wrote:
Hi Linus,
c. setitimer() can be used only once in a given process, you can have
up to 32 (configurable) POSIX timers at the same time in your process.
Why is there a limit? With such a small limit, any library that wants
to use its own private timers is going to
On Sat, 3 Feb 2001, Jamie Lokier wrote:
Robert H. de Vries wrote:
Hi Linus,
c. setitimer() can be used only once in a given process, you can have
up to 32 (configurable) POSIX timers at the same time in your process.
Why is there a limit? With such a small limit, any library that
6 matches
Mail list logo
