On Fri, 02 Jul 2004 10:12:12 +1200 Rex Johnston <[EMAIL PROTECTED]> wrote:
> Nick Rout wrote: > > >My IBM T20 laptop running gentoo with kde just did a weird thing. A > >warning came up that the battery was going flat and suddenly kde > >disappeared, and went back to the kdm login screen. I plugged it in and > >logged in to X/kde again. > > > >Before this happenned I was running some updates (emerge -U world) in > >some kde konsole windows. When I logged back in to kde I was about to > >start the emerge again (thinking it was lost because the controlling tty > >had disappeared when kde closed down), and noticed that cpu load was way > >up. A quick ps ax revealed the emerge was still running, and its > >controlling tty was listed as ? > > > >Is this some sort of standard behaviour? Other than using kill, how do I > >control these lost processes? > > > > > > Processes will get a HUP signal when their controlling tty disappears. > Some will die, some will ignore it, you can force > this with "nohup". There is no way of regaining control over a > detatched process. I suggest you use "screen" next time. I would have used screen if I knew kde was going to disappear like that. in fact there were 21 emerges stacked up by emerge -Up world, and only the one that was running at the time survived, and when it finished the emerging stopped. > > Cheers, Rex -- Nick Rout <[EMAIL PROTECTED]>
