From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Michael Richardson <mcr@sandelman.ottawa.on.ca>,
Henrik Nordstrom <uml@hno.marasystems.com>
Subject: Re: [uml-devel] T-mode processes
Date: Mon, 4 Oct 2004 20:22:22 +0200 [thread overview]
Message-ID: <200410042022.22838.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <30745.1096828767@marajade.sandelman.ottawa.on.ca>
On Sunday 03 October 2004 20:39, Michael Richardson wrote:
> >>>>> "Henrik" == Henrik Nordstrom <uml@hno.marasystems.com> writes:
>
> Henrik> Any way, sending a SIGCONT to the stopped process gets it
> Henrik> going again, or killed in case a SIGKILL or other terminal
> Henrik> action is pending.
>
> Our test bed produces a dozen of these every night.
> If someone has an idea on how to get better intel on this, I'm happy
> to cooperate.
If you want to change the behaviour on such a point, you should convince
top-level hackers on the LKML. Quite frankly, I guess that they will say
'NO'; and they will add "Who ever said that SIGKILL always works?". And if Al
Viro reads your post, his answer could be very bad (Al Viro is famous for the
way he flames newbie kernel hackers).
That said, this just means you need to fix the automated reaper. Changing this
in the SKAS patch is not an option (I don't have time to describe this). Even
because I think the behaviour is correct, and it's hard to change that.
Bye
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-10-04 18:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-03 0:26 [uml-devel] T-mode processes Michael Richardson
2004-10-03 10:41 ` Henrik Nordstrom
2004-10-03 17:26 ` Michael Richardson
2004-10-03 17:55 ` Henrik Nordstrom
2004-10-03 18:39 ` Michael Richardson
2004-10-04 18:22 ` BlaisorBlade [this message]
2004-10-04 22:40 ` Michael Richardson
2004-10-03 15:04 ` BlaisorBlade
2004-10-03 17:44 ` Michael Richardson
2004-10-04 18:57 ` BlaisorBlade
2004-10-04 20:25 ` Henrik Nordstrom
2004-10-05 18:51 ` BlaisorBlade
2004-10-06 0:00 ` Henrik Nordstrom
2004-10-06 19:45 ` BlaisorBlade
2004-10-14 16:46 ` BlaisorBlade
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=200410042022.22838.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--cc=mcr@sandelman.ottawa.on.ca \
--cc=uml@hno.marasystems.com \
--cc=user-mode-linux-devel@lists.sourceforge.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