[K12OSN] Kill User processes on log-off

Rob Owens hick518 at yahoo.com
Wed Feb 23 15:11:18 UTC 2005


On my system if I attempt to log in while I'm already
logged in somewhere else, gdm notifies me and asks
something like "abort or log in anyway?".  I guess
that could be changed to "kill the other session or
log in anyway".  Well I don't know how to do it, but
I'm sure it could be done...

-Rob

--- Daniel Hedblom <daniel.hedblom at skola.solleftea.se>
wrote:

> I dont know if thats such a good idea, what if i
> want to login from two places
> at once? The user ps should be killed at logout or
> at disconnected session,
> killing them at login is, well, backwards. The same
> issue is making linux look
> unstable if i use it at a normal desktop extensively
> under longer periods. I
> have seen this behaviour on Gentoo, Redhat FC1, 2
> and 3 and Ubuntu Linux. The
> common dominator is that i have used GDM on them
> all.
> 
> Why the processes wont die i dont know but i suspect
> that they are just left
> hanging totally unwitting the state of the session. 
> 
> Maybe i should just shut up and get my behind on
> track learning programming.
> 
> =)
> 
> /daniel
> 
> Citerar Rob Owens <hick518 at yahoo.com>:
> 
> > How about running a script like this at login
> time,
> > instead of at logout time?  Or maybe at both login
> and
> > logout?
> > 
> > Why is it that the processes don't die, anyway?
> > 
> > -Rob
> > 
> > --- Daniel Hedblom
> <daniel.hedblom at skola.solleftea.se>
> > wrote:
> > 
> > > Hi!
> > > 
> > > The problem with this solution is that it only
> works
> > > if the user has logged out.
> > > For example a pulled powercord or a network
> failiure
> > > will bypass the Postsession
> > > script. Due to a problem (feature?) in gdm
> (Gnome
> > > Display Manager) the session
> > > isnt cleaned up. There are a bug filed on this
> so if
> > > they find a fix i think we
> > > should use it on ltsp. I have had numerous
> clients
> > > who cant log in or experience
> > > strange errors in ooffice and other apps in
> because
> > > of orphaned processes. This
> > > have most often occured after one of the client
> has
> > > died or lost connectivity.
> > > 
> > > If anyone has a solution to this im happy as a
> pig
> > > =)
> > > 
> > > http://bugzilla.gnome.org/show_bug.cgi?id=152906
> > > http://bugzilla.gnome.org/show_bug.cgi?id=152907
> > > 
> > > /daniel
> > > 


	
		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - You care about security. So do we. 
http://promotions.yahoo.com/new_mail




More information about the K12OSN mailing list