Would it not be possible to have a script run at Login that kills all Processes for
that User before anything else runs?
> Date: Sun, 10 Mar 2002 17:01:45 -0500 (EST)
> From: <[EMAIL PROTECTED]>
> To: Zak McGregor <[EMAIL PROTECTED]>
> cc: <[EMAIL PROTECTED]>
> Subject: Re: [Ltsp-discuss] Ownerless processes
>
> Zak,
>
> If only it were that easy :)
>
> As I understand it, it is really a function of the display manager
> to kill any running tasks if a user dissappears. Really outside
> the scope of the LTSP. Although I agree that it is important
> for us.
>
> It seems that GDM is the display manager that causes the most
> problems, based on reports from the field, and my own experiences.
>
> On occasion, I've turned off a terminal, waited 30
> minutes, turned it back on and logged in, only to find my
> previously running processes still running! This was when
> using GDM.
>
> I'm now using KDM and have never seen the problem occur.
>
> Jim McQuillan
> [EMAIL PROTECTED]
>
>
> On Sun, 10 Mar 2002, Zak McGregor wrote:
>
> > Hi all
> >
> > OK, that's not quite an accurate description, but when users simply
> > switch off their terminals, their processes don't seem to
> die along with
> > them. Searching the ltsp-discuss archives yielded a few options for
> > dealing with these orphaned processes, but they all seem to
> be slightly
> > dodgy in terms of how they determine which users are idle
> and which not
> > etc. Is there a way to set up ltsp so that all processes
> are tied to the
> > initial login of the user, and so that when that process
> dies all other
> > processes of that user die with it?
> >
> > Thanks
> >
> > Cheers
> >
> > Zak
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.openprojects.net
