Subject: Re: [vserver] Wierd SIGTERM problem.
From: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date: Wed, 17 Oct 2007 04:49:29 -0700

On Wed, Oct 17, 2007 at 04:19:05AM -0700, Robin Lee Powell wrote:
> 1192618965.590008 --- SIGTERM (Terminated) @ 0 (0) ---
> 1192618965.590136 ioctl(8, TCXONC, TCOON) = 0
> 1192618965.590192 rt_sigprocmask(SIG_BLOCK, [INT], [TERM], 8) = 0
> 1192618965.590252 ioctl(8, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig -icanon
-echo ...}) = 0
> 1192618965.591181 +++ killed by SIGKILL +++

Sometimes this happens instead, generally to a different process
than "prompt":

1192620141.967353 read(11, 0x84de9c8, 4096) = ? ERESTARTSYS (To be restarted)
1192621140.698637 --- SIGTERM (Terminated) @ 0 (0) ---

Also, strace -ff gives a lot of:

    umovestr: Input/output error

but I don't know if that's relevant.

-Robin

-- 
Lojban Reason #17: http://en.wikipedia.org/wiki/Buffalo_buffalo
Proud Supporter of the Singularity Institute - http://singinst.org/
http://www.digitalkingdom.org/~rlpowell/ *** http://www.lojban.org/