From: Andrew Morton <andrewm@uow.edu.au>
To: John Fremlin <vii@penguinpowered.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Unified power management userspace policy
Date: Wed, 10 Jan 2001 01:13:53 +1100 [thread overview]
Message-ID: <3A5B1CA1.3B7402AE@uow.edu.au> (raw)
In-Reply-To: <m2lmsld4rk.fsf@boreas.yi.org.> <3A5AED76.B2F60F8D@uow.edu.au>, Andrew Morton's message of "Tue, 09 Jan 2001 21:52:38 +1100" <m27l44x239.fsf@boreas.yi.org.>
John Fremlin wrote:
>
> Hi!
>
> Andrew Morton <andrewm@uow.edu.au> writes:
>
> > Could you please use call_usermodehelper() in this patch
> > rather than exec_usermodehelper()? I want to kill
> > exec_usermodehelper() sometime.
>
> The reason I used exec_usermodehelper is that I wanted to waitpid on
> the process to see how it exited. Am I still allowed to do that if it
> runs as a child of keventd?
Oh foo. I missed that.
In the patch-which-didn't-make-it, yes, it can be called
synchronously. Or you can be called back with the exit
code when the subprocess exits. It does all the waitpid
stuff, the signal management, handles chrootedness, etc.
But that's vapourware now.
In the current implementation of call_usermodehelper(),
it looks like the commentary is incorrect - it returns
a negative error code or the subprocess's pid, but you
can't wait on that because it's parented by keventd.
Sorry for the noise - stick with what you have now.
-
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-01-09 14:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-08 23:05 John Fremlin
2001-01-09 10:52 ` Andrew Morton
2001-01-09 13:54 ` John Fremlin
2001-01-09 14:13 ` Andrew Morton [this message]
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=3A5B1CA1.3B7402AE@uow.edu.au \
--to=andrewm@uow.edu.au \
--cc=linux-kernel@vger.kernel.org \
--cc=vii@penguinpowered.com \
/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
all inboxes | Powered by JetHome®