> i'm not really sure what's going on. perhaps init is missing/dropping
> a SIGCHLD notification? you could check it's signal disposition via
> "psig <init_pid>".
root at bigmclargehuge:~ > psig 1011 | grep SIGCHLD
root at bigmclargehuge:~ >
If I understood the idea behind full output right, and then look at
this, it appears that it isn't even caught.
> it would also be interesting to have a truss output for init to see
> if it does get a SIGCHLD. to do that you'd have to stop init when
> booting the zone.
> zoneadm -z ubuntu halt
> dtrace -w -n 'syscall:::return/execname == "init" && zonename ==
> "ubuntu"/{stop(); trace(pid); exit(0);}'
> zoneadm -z ubuntu boot
>
> and then attach to it with truss
> truss -a -o ubuntu.init.txt -p <init_pid>
I've attached the full output. I can't figure out much from it, but it
appears that init just goes to sleep and waits for something. Then the
zone halt happens, pretty short, too.
-mg
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ubuntu_psig.txt
URL:
<http://mail.opensolaris.org/pipermail/brandz-discuss/attachments/20071005/68160254/attachment.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ubuntu.init.txt
URL:
<http://mail.opensolaris.org/pipermail/brandz-discuss/attachments/20071005/68160254/attachment-0001.txt>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 648 bytes
Desc: OpenPGP digital signature
URL:
<http://mail.opensolaris.org/pipermail/brandz-discuss/attachments/20071005/68160254/attachment.bin>
