From: Joe Marzot <gmarzot@nortelnetworks.com>
To: Jeff Dike <jdike@addtoit.com>
Cc: Joe Marzot <gmarzot@nortelnetworks.com>,
BlaisorBlade <blaisorblade_spam@yahoo.it>,
user-mode-linux-devel@lists.sourceforge.net, "Smith,
Paul [BL60:NP52:EXCH]" <pausmith@americasm01.nt.com>
Subject: Re: [uml-devel] handle_trap - failed to wait at end of syscall
Date: Wed, 15 Sep 2004 15:35:03 -0400 [thread overview]
Message-ID: <41489967.1090307@nortelnetworks.com> (raw)
In-Reply-To: 200409142123.i8ELN34W004063@ccure.user-mode-linux.org
Jeff Dike wrote:
> gmarzot@nortelnetworks.com said:
>
>>In our case the UML is launched like this:
>>perl script
>> my $pid = fork();
>> if ($pid == 0) {
>> setpgrp(); # give all UMLs the same group id so I can renice them
>> exec($cmd);
>
>
> I think I understand what's happening. You are (unwittingly) sending UML
> (and every process that belongs to it) a HUP when you, in effect, detach it
> from its parent terminal.
where am I detaching from the parent terminal?
I just did a little test and instead of invoking UML I start a little
perl script in exactly the same way as above to catch SIGHUP...but no
SIGHUP arrives.
>
> My first thought was that SIGHUP isn't disabled in the userspace process,
> and it should be, but it is, so I don't know why it's even being seen by
> the ptracer. It should only see signals which are enabled in the child.
more oddness.
>
> In the meantime, while we figure this out, you might try just adding "nohup"
> to the beginning of your $cmd.
originally tried this but something bad happened...forget which I could
go back and see ... and try setsid as the other poster suggested.
regards, GSM
>
> Jeff
>
>
>
-------------------------------------------------------
This SF.Net email is sponsored by: thawte's Crypto Challenge Vl
Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam
Camcorder. More prizes in the weekly Lunch Hour Challenge.
Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2004-09-15 19:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-11 15:32 [uml-devel] debugging UML cores Joe Marzot
2004-08-12 5:41 ` Jeff Dike
2004-08-12 15:21 ` Joe Marzot
2004-08-12 16:56 ` Jeff Dike
2004-08-12 16:16 ` Joe Marzot
2004-08-12 15:36 ` Joe Marzot
2004-08-12 15:47 ` Joe Marzot
2004-08-13 15:46 ` [uml-devel] handle_trap - failed to wait at end of syscall [was Re: [uml-devel] debugging UML cores] Joe Marzot
2004-08-13 18:01 ` Joe Marzot
2004-08-13 21:47 ` Jeff Dike
2004-08-16 17:47 ` [uml-devel] Re: handle_trap - failed to wait at end of syscall [was Re: [uml- devel] " Joe Marzot
2004-08-16 19:25 ` Joe Marzot
2004-08-16 19:53 ` D. Bahi
2004-08-17 5:26 ` Jeff Dike
2004-08-20 11:46 ` handle_trap - failed to wait at end of syscall [was Re: [uml-devel] " BlaisorBlade
2004-09-13 15:39 ` [uml-devel] handle_trap - failed to wait at end of syscall Joe Marzot
2004-09-13 19:39 ` BlaisorBlade
2004-09-13 22:14 ` Jeff Dike
2004-09-14 10:41 ` BlaisorBlade
2004-09-14 16:09 ` Joe Marzot
2004-09-14 21:23 ` Jeff Dike
2004-09-15 5:00 ` Richard Potter
2004-09-15 19:35 ` Joe Marzot [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=41489967.1090307@nortelnetworks.com \
--to=gmarzot@nortelnetworks.com \
--cc=blaisorblade_spam@yahoo.it \
--cc=jdike@addtoit.com \
--cc=pausmith@americasm01.nt.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.