[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Interesting ps -ax listing
From:       Dave Feustel <dfeustel () mindspring ! com>
Date:       2005-11-30 15:40:38
Message-ID: 200511301040.39451.dfeustel () mindspring ! com
[Download RAW message or body]

On Wednesday 30 November 2005 10:28, David Faure wrote:
> On Wednesday 30 November 2005 13:49, Dave Feustel wrote:
> > On Wednesday 30 November 2005 07:05, Otto Moerbeek wrote:
> > > On Wed, 30 Nov 2005, Dave Feustel wrote:
> > > > While running kde 3.4.2 on OpenBSD 3.8, upon logging out from my
> > > > normal user id and then logging back in with a new user id and
> > > > executing ps -ax, I found an instance of kde kicker running before I
> > > > had invoked startkde as the new user. I was not able to delete the
> > > > process using kill -9, so I logged out, logged back in under the
> > > > previous user name and then was able to delete the kicker task using
> > > > kill -9. My understanding is that all user processes (eg, kde
> > > > processes) are terminated when the user logs out. Is that correct?
> > > > Any ideas as to how the user process survived the logout?
> > >
> > > If a process detaches from the terminal, it will survive. Another way
> > > is using nohup(1).
> > >
> > > If kde leaves processes hanging around, it looks like a bug in kde.
>
> Except that any program with an X connection dies when the X connection
> goes away. But maybe logging out on Dave's system doesn't really kill X?

Note I am using neither xdm nor kdm for logins. I login in console mode and
then run startkde. In this case I had first logged out of kde by clicking on 
the "logout" item in the kde menu (which dropped me to console mode) and then 
doing an exit.

The old user process that was still running after logging in with the new user 
id was a 'kicker' process.
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]