From: andrey100100100@gmail.com
To: 9fans@9fans.net
Subject: Re: [9fans] syscall silently kill processes
Date: Sat, 18 Jun 2022 19:57:44 +0300 [thread overview]
Message-ID: <658d1591a1abef7c4a85ea3bbf23777b38247893.camel@gmail.com> (raw)
In-Reply-To: <64a85bad-7ab-fb6-6517-acfafa819bc@SDF.ORG>
В Сб, 18/06/2022 в 08:37 +0000, adr пишет:
> On Sat, 18 Jun 2022, andrey100100100@gmail.com wrote:
>
> > ---------------------------------------------
> >
> > cpu% 6.out | grep end | wc -l
> > 33
> >
> >
> > Problem in unregistered handlers.
>
> But unregistered handlers shouldn't be a problem. The process is
> been killed when alarm sends the note. That's why the code worked
> removing the read statement, the alarm is set off and the note is
> not sent before the process ends. I just don't see why the process
> is been killed.
The process dies, because the handler that suppresses the default
behavior on note 'alarm' is not registered. And the default behavior is
death.
> The documentation describes another behaivor. To
> me it smells like bug barbecue (corrupted onnote?). Maybe I got
> something wrong, bear with me.
>
> > > Note that you could register the handler in threadmain and avoid
> > > completely this issue, but as I said before, something seems
> > > wrong
> > > to me here.
> >
> > I'm don't understand how handler in threadmain would solve the
> > problem.
> > I need in 'alarm' on per process basis.
>
> You need alarm() in every process, but you don't need to register the
> same handler 80 times!
Perhaps I need different handlers for different processes.
Or, for some processes, I need a default behavior, and for some others,
a handler.
>
> adr.
>
Regards,
Andrej
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tfa6823048ad90a21-Mc5582399d6c559ec53eddd59
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2022-06-18 16:58 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 9:37 andrey100100100
2022-06-17 13:46 ` Thaddeus Woskowiak
2022-06-17 14:11 ` Jacob Moody
2022-06-17 14:39 ` Thaddeus Woskowiak
2022-06-17 15:06 ` andrey100100100
2022-06-17 16:08 ` Skip Tavakkolian
2022-06-17 16:11 ` Skip Tavakkolian
2022-06-17 16:16 ` Skip Tavakkolian
2022-06-17 17:42 ` adr
2022-06-17 16:11 ` Jacob Moody
2022-06-17 18:48 ` andrey100100100
2022-06-17 19:28 ` Jacob Moody
2022-06-17 21:15 ` adr
2022-06-18 6:40 ` andrey100100100
2022-06-18 8:37 ` adr
2022-06-18 9:22 ` adr
2022-06-18 12:53 ` Jacob Moody
2022-06-18 22:03 ` andrey100100100
2022-06-19 5:54 ` adr
2022-06-19 6:13 ` Jacob Moody
2022-06-18 22:22 ` andrey100100100
2022-06-18 16:57 ` andrey100100100 [this message]
2022-06-19 2:40 ` adr
2022-06-19 5:01 ` adr
2022-06-19 8:52 ` andrey100100100
2022-06-19 10:32 ` adr
2022-06-19 11:40 ` andrey100100100
2022-06-19 12:01 ` andrey100100100
2022-06-19 15:10 ` andrey100100100
2022-06-19 16:41 ` adr
2022-06-19 21:22 ` andrey100100100
2022-06-19 21:26 ` andrey100100100
2022-06-20 4:41 ` adr
2022-06-20 5:39 ` andrey100100100
2022-06-20 5:59 ` adr
2022-06-20 15:56 ` andrey100100100
2022-06-20 22:29 ` Skip Tavakkolian
2022-06-21 7:07 ` andrey100100100
2022-06-21 11:26 ` adr
2022-06-21 13:03 ` andrey100100100
2022-06-21 13:22 ` adr
2022-06-28 15:28 ` adr
2022-06-28 16:43 ` ori
2022-06-28 18:19 ` adr
2022-06-28 18:28 ` adr
2022-06-28 19:09 ` andrey100100100
2022-06-28 19:42 ` adr
2022-06-29 13:14 ` adr
2022-06-21 13:47 ` andrey100100100
2022-06-21 7:22 ` adr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=658d1591a1abef7c4a85ea3bbf23777b38247893.camel@gmail.com \
--to=andrey100100100@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).