On 3/1/22 4:15 PM, David Laight wrote:
> From: Denys Vlasenko
>> Sent: 01 March 2022 21:57
>>
>> On Tue, Mar 1, 2022 at 5:39 PM Denys Vlasenko
>> wrote:
>> > Meanwhile: what "timeout" is doing is it tries to get out
>> > of the way of the PROG to be launched so that timeout's parent
>> >
On 3/1/22 1:45 PM, Denys Vlasenko wrote:
> On Tue, Mar 1, 2022 at 6:52 PM Steffen Nurpmeso wrote:
>> David Laight wrote in
>> :
>> |From: Denys Vlasenko
>> |> Sent: 01 March 2022 16:40
>> |> On Tue, Feb 15, 2022 at 12:31 PM Rob Landley wrote:
>> |>> On 2/14/22 10:09 AM, Roberto A.
David Laight wrote in
<3c1a02d162c34e908af85ac008a87...@acums.aculab.com>:
|From: Steffen Nurpmeso
|> Sent: 01 March 2022 17:49
|> David Laight wrote in
|> :
|>|From: Denys Vlasenko
|>|> Sent: 01 March 2022 16:40
|>|> On Tue, Feb 15, 2022 at 12:31 PM Rob Landley wrote:
|>|>> On 2/14/22
Denys Vlasenko wrote in
:
|On Tue, Mar 1, 2022 at 6:52 PM Steffen Nurpmeso wrote:
|> David Laight wrote in
|> :
|>|From: Denys Vlasenko
|>|> Sent: 01 March 2022 16:40
|>|> On Tue, Feb 15, 2022 at 12:31 PM Rob Landley wrote:
|>|>> On 2/14/22 10:09 AM, Roberto A. Foglietta wrote:
|> ...
From: Denys Vlasenko
> Sent: 01 March 2022 22:40
>
> On Tue, Mar 1, 2022 at 11:15 PM David Laight wrote:
> > From: Denys Vlasenko
> > > and a separate "spawn 40k 'sleep 0.03'" loop
> > > seems to indicate that openat(fd, ".") on the exited
> > > /proc/PID fails, and continues to fail
> > > even
On Tue, Mar 1, 2022 at 11:15 PM David Laight wrote:
> From: Denys Vlasenko
> > and a separate "spawn 40k 'sleep 0.03'" loop
> > seems to indicate that openat(fd, ".") on the exited
> > /proc/PID fails, and continues to fail
> > even if another process with this PID exists
> > again (pid was
From: Steffen Nurpmeso
> Sent: 01 March 2022 17:49
...
>
> David Laight wrote in
> :
> |From: Denys Vlasenko
> |> Sent: 01 March 2022 16:40
> |> On Tue, Feb 15, 2022 at 12:31 PM Rob Landley wrote:
> |>> On 2/14/22 10:09 AM, Roberto A. Foglietta wrote:
> ...
> |> My memory is hazy on this,
From: Denys Vlasenko
> Sent: 01 March 2022 21:57
>
> On Tue, Mar 1, 2022 at 5:39 PM Denys Vlasenko
> wrote:
> > Meanwhile: what "timeout" is doing is it tries to get out
> > of the way of the PROG to be launched so that timeout's parent
> > sees PROG (not timeout) as a child. E.g. it can send
On Tue, Mar 1, 2022 at 5:39 PM Denys Vlasenko wrote:
> Meanwhile: what "timeout" is doing is it tries to get out
> of the way of the PROG to be launched so that timeout's parent
> sees PROG (not timeout) as a child. E.g. it can send signals
> to it, get waitpid notifications if PROG has been
On Tue, Mar 1, 2022 at 6:52 PM Steffen Nurpmeso wrote:
> David Laight wrote in
> :
> |From: Denys Vlasenko
> |> Sent: 01 March 2022 16:40
> |> On Tue, Feb 15, 2022 at 12:31 PM Rob Landley wrote:
> |>> On 2/14/22 10:09 AM, Roberto A. Foglietta wrote:
> ...
> |> My memory is hazy on this,
On 3/1/22 10:39 AM, Denys Vlasenko wrote:
> On Tue, Feb 15, 2022 at 12:31 PM Rob Landley wrote:
>> On 2/14/22 10:09 AM, Roberto A. Foglietta wrote:
>> > However, if this bug shows-up, probably it means that the system has
>> > a lot of processes running and a lot of processes created and
>> >
Hello.
..despite that particular timeout(1), i have not looked..
David Laight wrote in
:
|From: Denys Vlasenko
|> Sent: 01 March 2022 16:40
|> On Tue, Feb 15, 2022 at 12:31 PM Rob Landley wrote:
|>> On 2/14/22 10:09 AM, Roberto A. Foglietta wrote:
...
|> My memory is hazy on this, but
From: Denys Vlasenko
> Sent: 01 March 2022 16:40
>
> On Tue, Feb 15, 2022 at 12:31 PM Rob Landley wrote:
> > On 2/14/22 10:09 AM, Roberto A. Foglietta wrote:
> > > However, if this bug shows-up, probably it means that the system has
> > > a lot of processes running and a lot of processes
On Tue, Feb 15, 2022 at 12:31 PM Rob Landley wrote:
> On 2/14/22 10:09 AM, Roberto A. Foglietta wrote:
> > However, if this bug shows-up, probably it means that the system has
> > a lot of processes running and a lot of processes created and
> > destroyed compared to the max PID available. Thus,
14 matches
Mail list logo
