Log off doesn end all user processes

Discussion:

Radek Bursztynowski

2014-04-16 11:50:14 UTC

Hello,

I have a problem with ending on server thin client LTSP session. When I log out from the server session I return to the LDM, but there are not closed my user processes on the server. After GNOME log out there are:

[***@tryandbuy pxelinux.cfg]# ps aux | grep radek
radek 10790 0.0 0.0 20040 680 ? S 13:22 0:00 dbus-launch --sh-syntax --exit-with-session
radek 10791 0.0 0.0 21816 1236 ? Ss 13:22 0:00 /bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
radek 10858 0.0 0.0 232924 6588 ? Ss 13:22 0:00 /usr/bin/seahorse-agent --variables
radek 10862 0.0 0.0 137360 2152 ? S 13:22 0:00 /usr/libexec/gvfsd
radek 10876 0.0 0.0 133864 5808 ? S 13:22 0:00 /usr/libexec/gconfd-2
radek 10906 0.0 0.0 24752 2032 ? S 13:22 0:00 /usr/lib64/xfce4/xfconf/xfconfd
radek 10929 0.0 0.0 238448 5640 ? S 13:22 0:00 Thunar --daemon
radek 10936 0.0 0.0 242892 2900 ? Ss 13:22 0:00 gnome-screensaver
radek 10943 0.0 0.0 328644 10784 ? Sl 13:22 0:00 /usr/libexec/polkit-gnome-authentication-agent-1
radek 10946 0.0 0.0 508884 10908 ? S 13:22 0:00 gnome-volume-control-applet
radek 10952 0.0 0.0 115096 4052 ? S 13:22 0:00 /usr/libexec/im-settings-daemon
radek 10975 0.0 0.0 251984 6792 ? S 13:22 0:00 gnome-power-manager
radek 10978 0.0 0.1 303344 18736 ? S 13:22 0:00 python /usr/share/system-config-printer/applet.py
radek 10986 0.0 0.0 362372 9840 ? S 13:22 0:00 gpk-update-icon
radek 10997 0.0 0.0 358308 6872 ? S 13:22 0:00 /usr/libexec/evolution/2.32/evolution-alarm-notify
radek 11119 0.0 0.0 40900 2232 ? S 13:22 0:00 /usr/libexec/gconf-im-settings-daemon
radek 11120 0.0 0.0 201512 2528 ? S 13:22 0:00 xfsettingsd
radek 11140 0.0 0.0 148776 3532 ? S 13:22 0:00 /usr/libexec/gvfs-gdu-volume-monitor
radek 11144 0.0 0.0 232436 2064 ? Sl 13:22 0:00 /usr/libexec/gvfs-afc-volume-monitor
radek 11147 0.0 0.0 150892 2196 ? S 13:22 0:00 /usr/libexec/gvfs-gphoto2-volume-monitor
radek 11149 0.0 0.0 146304 3228 ? S 13:22 0:00 /usr/libexec/gvfsd-trash --spawner :1.2 /org/gtk/gvfs/exec_spaw/0
radek 11297 0.0 0.0 356628 10964 ? S 13:28 0:00 /usr/libexec/notification-daemon

After KDE log out:
[***@tryandbuy pxelinux.cfg]# ps aux | grep radek

[***@tryandbuy pxelinux.cfg]# ps aux | grep radek
radek 11832 0.0 0.0 20040 692 ? S 13:40 0:00 dbus-launch --sh-syntax --exit-with-session
radek 11833 0.0 0.0 21668 1208 ? Ss 13:40 0:00 /bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
radek 11900 0.0 0.0 235144 6708 ? Ss 13:40 0:00 /usr/bin/seahorse-agent --variables
radek 11908 0.0 0.0 137360 2104 ? S 13:40 0:00 /usr/libexec/gvfsd
radek 11914 0.0 0.0 133848 5768 ? S 13:40 0:00 /usr/libexec/gconfd-2
radek 12102 0.0 0.0 115096 4052 ? S 13:40 0:00 /usr/libexec/im-settings-daemon
radek 12258 0.0 0.0 40900 2232 ? S 13:40 0:00 /usr/libexec/gconf-im-settings-daemon

Could anybody advice me how to close all processes within log out?

Best regards,
Radek

Jim Kinney

2014-04-16 12:58:42 UTC

Permalink

All of those _SHOULD_ close when you log out. You can add a script that
does a kill -9 on all the PIDs with your UID as owner.

However, those processes can hang around if a session crashes. They may be
stale. I also noticed you have a Thunar process. That's not part of normal
gnome so it may be holding open the gnome stuff.

run this:

ps aux | grep radek | awk '{print $2}' | xargs kill -9

That will kill all the processes. Now launch a TC session and log right
back out, wait a minute and then ps aux | grep radek

Which base server OS are you running?

On Wed, Apr 16, 2014 at 7:50 AM, Radek Bursztynowski <

Post by Radek Bursztynowski
Hello,
I have a problem with ending on server thin client LTSP session. When I
log out from the server session I return to the LDM, but there are not
radek 10790 0.0 0.0 20040 680 ? S 13:22 0:00
dbus-launch --sh-syntax --exit-with-session
radek 10791 0.0 0.0 21816 1236 ? Ss 13:22 0:00
/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
radek 10858 0.0 0.0 232924 6588 ? Ss 13:22 0:00
/usr/bin/seahorse-agent --variables
radek 10862 0.0 0.0 137360 2152 ? S 13:22 0:00 /usr/libexec/gvfsd
radek 10876 0.0 0.0 133864 5808 ? S 13:22 0:00 /usr/libexec/gconfd-2
radek 10906 0.0 0.0 24752 2032 ? S 13:22 0:00
/usr/lib64/xfce4/xfconf/xfconfd
radek 10929 0.0 0.0 238448 5640 ? S 13:22 0:00 Thunar --daemon
radek 10936 0.0 0.0 242892 2900 ? Ss 13:22 0:00 gnome-screensaver
radek 10943 0.0 0.0 328644 10784 ? Sl 13:22 0:00
/usr/libexec/polkit-gnome-authentication-agent-1
radek 10946 0.0 0.0 508884 10908 ? S 13:22 0:00
gnome-volume-control-applet
radek 10952 0.0 0.0 115096 4052 ? S 13:22 0:00
/usr/libexec/im-settings-daemon
radek 10975 0.0 0.0 251984 6792 ? S 13:22 0:00 gnome-power-manager
radek 10978 0.0 0.1 303344 18736 ? S 13:22 0:00 python
/usr/share/system-config-printer/applet.py
radek 10986 0.0 0.0 362372 9840 ? S 13:22 0:00 gpk-update-icon
radek 10997 0.0 0.0 358308 6872 ? S 13:22 0:00
/usr/libexec/evolution/2.32/evolution-alarm-notify
radek 11119 0.0 0.0 40900 2232 ? S 13:22 0:00
/usr/libexec/gconf-im-settings-daemon
radek 11120 0.0 0.0 201512 2528 ? S 13:22 0:00 xfsettingsd
radek 11140 0.0 0.0 148776 3532 ? S 13:22 0:00
/usr/libexec/gvfs-gdu-volume-monitor
radek 11144 0.0 0.0 232436 2064 ? Sl 13:22 0:00
/usr/libexec/gvfs-afc-volume-monitor
radek 11147 0.0 0.0 150892 2196 ? S 13:22 0:00
/usr/libexec/gvfs-gphoto2-volume-monitor
radek 11149 0.0 0.0 146304 3228 ? S 13:22 0:00
/usr/libexec/gvfsd-trash --spawner :1.2 /org/gtk/gvfs/exec_spaw/0
radek 11297 0.0 0.0 356628 10964 ? S 13:28 0:00
/usr/libexec/notification-daemon
radek 11832 0.0 0.0 20040 692 ? S 13:40 0:00
dbus-launch --sh-syntax --exit-with-session
radek 11833 0.0 0.0 21668 1208 ? Ss 13:40 0:00
/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
radek 11900 0.0 0.0 235144 6708 ? Ss 13:40 0:00
/usr/bin/seahorse-agent --variables
radek 11908 0.0 0.0 137360 2104 ? S 13:40 0:00 /usr/libexec/gvfsd
radek 11914 0.0 0.0 133848 5768 ? S 13:40 0:00 /usr/libexec/gconfd-2
radek 12102 0.0 0.0 115096 4052 ? S 13:40 0:00
/usr/libexec/im-settings-daemon
radek 12258 0.0 0.0 40900 2232 ? S 13:40 0:00
/usr/libexec/gconf-im-settings-daemon
Could anybody advice me how to close all processes within log out?
Best regards,
Radek
_______________________________________________
K12OSN mailing list
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>

--
--
James P. Kinney III

Every time you stop a school, you will have to build a jail. What you gain
at one end you lose at the other. It's like feeding a dog on his own tail.
It won't fatten the dog.
- Speech 11/23/1900 Mark Twain

*http://heretothereideas.blogspot.com/
<http://heretothereideas.blogspot.com/>*

jomegat

2014-04-16 13:06:26 UTC

Permalink

Post by Jim Kinney
ps aux | grep radek | awk '{print $2}' | xargs kill -9

Here's an easier option:

pkill -u radek

Also,

pkill -u radek --signal 9

--
Jim Thomas (j omegat t)
It's easier to outsmart people than it is to outdumb them.
- Scott Meyers

Jim Kinney

2014-04-16 13:10:41 UTC

Permalink

nice! New tool.

Post by jomegat

Post by Jim Kinney
ps aux | grep radek | awk '{print $2}' | xargs kill -9

pkill -u radek
Also,
pkill -u radek --signal 9
--
Jim Thomas (j omegat t)
It's easier to outsmart people than it is to outdumb them.
- Scott Meyers
_______________________________________________
K12OSN mailing list
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>

jomegat

2014-04-16 13:20:27 UTC

Permalink

Post by Jim Kinney
nice! New tool.

It is a nice tool. Unfortunately, using it in this case treats the
symptom rather than the disease. But sometimes that's what you need to do.

Post by Jim Kinney
ps aux | grep radek | awk '{print $2}' | xargs kill -9
pkill -u radek
Also,
pkill -u radek --signal 9
--
Jim Thomas (j omegat t)
It's easier to outsmart people than it is to outdumb them.
- Scott Meyers
_______________________________________________
K12OSN mailing list
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>
--
--
James P. Kinney III
////
////Every time you stop a school, you will have to build a jail. What
you gain at one end you lose at the other. It's like feeding a dog on
his own tail. It won't fatten the dog.
- Speech 11/23/1900 Mark Twain
////
http://heretothereideas.blogspot.com/
////
_______________________________________________
K12OSN mailing list
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>

--
Jim Thomas (j omegat t)
It's easier to outsmart people than it is to outdumb them.
- Scott Meyers

Veli-Matti Lintu

2014-04-16 13:18:07 UTC

Permalink

Hello,

There's a tool called xexit that you could try. It triggers a script to clean
up user's processes when the session has died for some reason or X does not
respond anymore.

There's more here:

http://labs.opinsys.com/blog/2011/03/22/killing-user-processes-with-xexit-on-ltsp-servers/

Happy hacking,

Veli-Matti

----- Original Message -----

Sent: Wednesday, April 16, 2014 2:50:14 PM
Subject: [K12OSN] Log off doesn end all user processes
Hello,
I have a problem with ending on server thin client LTSP session. When I log
out from the server session I return to the LDM, but there are not closed my
radek 10790 0.0 0.0 20040 680 ? S 13:22 0:00 dbus-launch --sh-syntax
--exit-with-session
radek 10791 0.0 0.0 21816 1236 ? Ss 13:22 0:00 /bin/dbus-daemon --fork
--print-pid 5 --print-address 7 --session
radek 10858 0.0 0.0 232924 6588 ? Ss 13:22 0:00 /usr/bin/seahorse-agent
--variables
radek 10862 0.0 0.0 137360 2152 ? S 13:22 0:00 /usr/libexec/gvfsd
radek 10876 0.0 0.0 133864 5808 ? S 13:22 0:00 /usr/libexec/gconfd-2
radek 10906 0.0 0.0 24752 2032 ? S 13:22 0:00 /usr/lib64/xfce4/xfconf/xfconfd
radek 10929 0.0 0.0 238448 5640 ? S 13:22 0:00 Thunar --daemon
radek 10936 0.0 0.0 242892 2900 ? Ss 13:22 0:00 gnome-screensaver
radek 10943 0.0 0.0 328644 10784 ? Sl 13:22 0:00
/usr/libexec/polkit-gnome-authentication-agent-1
radek 10946 0.0 0.0 508884 10908 ? S 13:22 0:00 gnome-volume-control-applet
radek 10952 0.0 0.0 115096 4052 ? S 13:22 0:00
/usr/libexec/im-settings-daemon
radek 10975 0.0 0.0 251984 6792 ? S 13:22 0:00 gnome-power-manager
radek 10978 0.0 0.1 303344 18736 ? S 13:22 0:00 python
/usr/share/system-config-printer/applet.py
radek 10986 0.0 0.0 362372 9840 ? S 13:22 0:00 gpk-update-icon
radek 10997 0.0 0.0 358308 6872 ? S 13:22 0:00
/usr/libexec/evolution/2.32/evolution-alarm-notify
radek 11119 0.0 0.0 40900 2232 ? S 13:22 0:00
/usr/libexec/gconf-im-settings-daemon
radek 11120 0.0 0.0 201512 2528 ? S 13:22 0:00 xfsettingsd
radek 11140 0.0 0.0 148776 3532 ? S 13:22 0:00
/usr/libexec/gvfs-gdu-volume-monitor
radek 11144 0.0 0.0 232436 2064 ? Sl 13:22 0:00
/usr/libexec/gvfs-afc-volume-monitor
radek 11147 0.0 0.0 150892 2196 ? S 13:22 0:00
/usr/libexec/gvfs-gphoto2-volume-monitor
radek 11149 0.0 0.0 146304 3228 ? S 13:22 0:00 /usr/libexec/gvfsd-trash
--spawner :1.2 /org/gtk/gvfs/exec_spaw/0
radek 11297 0.0 0.0 356628 10964 ? S 13:28 0:00
/usr/libexec/notification-daemon
radek 11832 0.0 0.0 20040 692 ? S 13:40 0:00 dbus-launch --sh-syntax
--exit-with-session
radek 11833 0.0 0.0 21668 1208 ? Ss 13:40 0:00 /bin/dbus-daemon --fork
--print-pid 5 --print-address 7 --session
radek 11900 0.0 0.0 235144 6708 ? Ss 13:40 0:00 /usr/bin/seahorse-agent
--variables
radek 11908 0.0 0.0 137360 2104 ? S 13:40 0:00 /usr/libexec/gvfsd
radek 11914 0.0 0.0 133848 5768 ? S 13:40 0:00 /usr/libexec/gconfd-2
radek 12102 0.0 0.0 115096 4052 ? S 13:40 0:00
/usr/libexec/im-settings-daemon
radek 12258 0.0 0.0 40900 2232 ? S 13:40 0:00
/usr/libexec/gconf-im-settings-daemon
Could anybody advice me how to close all processes within log out?
Best regards,
Radek
_______________________________________________
K12OSN mailing list
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>

Radek Bursztynowski

2014-04-16 15:07:19 UTC

Permalink

Many thanks to all for advices.
Yes, I use pkill -U $USER for loging out LTSP client from the server.
Every time I check is the user is loged in from thin client or from the server directly and for LTSP session I use pkill, for directed session standard log out GNOME, XFCE or KDE program. It works fine with Scientific Linux 6.1 or CentOS 6.4 thin clent image. But I have several old machines which have to use old thin client image (Fedora 11 - i586). And pkill -U $USER with Fedora 11 thin client image kills all user processes but LDM on thin client couldn't refresh and I can see black screen only. When I use Ctrl+Alt+Backspace keys everything back to the norm and LDM reloads. It isn't clear solution for the users who use Fedora 11 thin client image with on old machines.

Let me add that when I log out using standard GNOME/XFCE/KDE logging out program on Fedora 11 image, LDM reloads well, but few user processes still run.

This is my real problem.

On the margin I noticed that pkill -U $USER doesn't umount breaks link with /home/$USER/.gvf. It breajs tar user home directory for simple bacakup. So, the first I umount /home/$USER/gvfs and the next is pkill.

Many thanks again for help, perhaps something else?

Radek

----- Original Message -----
From: jomegat <***@jomegat.com>
Sent: Wed, 4/16/2014 3:20pm
To: "Support list for open source software in schools." <***@redhat.com>
Subject: Re: [K12OSN] Log off doesn end all user processes

On 04/16/2014 09:10 AM, Jim Kinney
wrote:

nice! New tool.

It is a nice tool. Unfortunately, using it in this case treats the
symptom rather than the disease. But sometimes that's what you need
to do.

On Wed, Apr 16, 2014 at 9:06 AM,
jomegat <***@jomegat.com>
wrote:

On 04/16/2014 08:58 AM, Jim Kinney wrote:

run this:

ps aux | grep radek | awk '{print $2}' | xargs kill -9

Here's an easier option:

pkill -u radek

Also,

pkill -u radek --signal 9

--

Jim Thomas (j omegat t)

It's easier to outsmart people than it is to outdumb
them.

- Scott
Meyers

_______________________________________________

K12OSN mailing list

***@redhat.com

https://www.redhat.com/mailman/listinfo/k12osn

For more info see <http://www.k12os.org>

--

--

James P. Kinney III

Every time you stop a school, you will
have to build a jail. What you gain at one end you lose at the
other. It's like feeding a dog on his own tail. It won't
fatten the dog.

- Speech 11/23/1900 Mark Twain

http://heretothereideas.blogspot.com/

_______________________________________________
K12OSN mailing list
***@redhat.com
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>

--
Jim Thomas (j omegat t)
It's easier to outsmart people than it is to outdumb them.
- Scott Meyers

_______________________________________________
K12OSN mailing list
***@redhat.com
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>;

e***@ekrotech.com

2014-04-16 18:33:36 UTC

Permalink

_______________________________________________
K12OSN mailing list
***@redhat.com
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>

Radek Bursztynowski

2014-04-16 20:36:43 UTC

Permalink

Emil,

Thanks for explanation. Let me add my feelings.
In my opinion newer thin client images (Scientific Linux 6.1, CentOS
6.4) reload LDM spontaneously when active session between thin client
and the server is broken. Owing to that pkill -U $USER works fine.
Fedora 11 thin image doesn't reload LDM spontaneously. So, I think the
solution is on the thin client image, not on the server site.

Pozdrawiam,
Radek

Killing processes using user name is just part of the solution.
Any Linux, process has a parent process, and if the parent process
dies, child process should get terminated too.
Key word: "should".
Problem arises if client process does not intercept the termination of
the parent process and stll runs, or is already dis-joined from the
group with the parent while going background, or created as parallel.
In case parent process dies and child does not end, "init" overtakes
parentship of the "orphaned" process, and you may need to search for
that processes to kill explicitly by name, but you need to know their
names (PID is not the good criteria).
IMHO all LDM created processes should NOT dis-join that group and
should react on the signal about parent death, ceasing to execute any
longer.
Again: "should".
Well, it may mean, that LTSP (LDM and childs) may need some
code-review focusing on process parentship handling at
creation/termination...
Kind regards
Emil Krotki
EkroTech
Mobile: +420 775 314 445
-------- Original Message --------
Subject: Re: [K12OSN] Log off doesn end all user processes
Date: Wed, April 16, 2014 4:07 pm
To: "Support list for open source software in schools."
Many thanks to all for advices.
Yes, I use pkill -U $USER for loging out LTSP client from the
server.
Every time I check is the user is loged in from thin client or
from the server directly and for LTSP session I use pkill, for
directed session standard log out GNOME, XFCE or KDE program.
It works fine with Scientific Linux 6.1 or CentOS 6.4 thin
clent image. But I have several old machines which have to use
old thin client image (Fedora 11 - i586). And pkill -U $USER
with Fedora 11 thin client image kills all user processes but
LDM on thin client couldn't refresh and I can see black screen
only. When I use Ctrl+Alt+Backspace keys everything back to
the norm and LDM reloads. It isn't clear solution for the
users who use Fedora 11 thin client image with on old
machines.
Let me add that when I log out using standard GNOME/XFCE/KDE
logging out program on Fedora 11 image, LDM reloads well, but
few user processes still run.
This is my real problem.
On the margin I noticed that pkill -U $USER doesn't umount
breaks link with /home/$USER/.gvf. It breajs tar user home
directory for simple bacakup. So, the first I
umount /home/$USER/gvfs and the next is pkill.
Many thanks again for help, perhaps something else?
Radek
----- Original Message -----
Sent: Wed, 4/16/2014 3:20pm
To: "Support list for open source software in schools."
Subject: Re: [K12OSN] Log off doesn end all user processes
On 04/16/2014 09:10 AM, Jim Kinney
nice! New tool.
It is a nice tool. Unfortunately, using it in this case treats
the
symptom rather than the disease. But sometimes that's what you
need
to do.
On Wed, Apr 16, 2014 at 9:06 AM,
ps aux | grep radek | awk '{print $2}' | xargs kill -9
pkill -u radek
Also,
pkill -u radek --signal 9
--
Jim Thomas (j omegat t)
It's easier to outsmart people than it is to outdumb
them.
- Scott
Meyers
_______________________________________________
K12OSN mailing list
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>
--
--
James P. Kinney III
Every time you stop a school, you will
have to build a jail. What you gain at one end you lose at the
other. It's like feeding a dog on his own tail. It won't
fatten the dog.
- Speech 11/23/1900 Mark Twain
http://heretothereideas.blogspot.com/
_______________________________________________
K12OSN mailing list
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>
--
Jim Thomas (j omegat t)
It's easier to outsmart people than it is to outdumb them.
- Scott Meyers
_______________________________________________
K12OSN mailing list
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>;
_______________________________________________
K12OSN mailing list
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>
_______________________________________________
K12OSN mailing list
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>

Joseph Bishay

2014-04-17 17:41:52 UTC

Permalink

Hello,

I have this same problem and I found the 'slay' command works
perfectly to resolve the leftover processes.

# slay username

Plus it's fun to tell the others that I had to 'slay' so-and-so :)

Info:
http://linuxpoison.blogspot.ca/2011/01/kills-all-of-users-processes-slay.html

Joseph

On Wed, Apr 16, 2014 at 7:50 AM, Radek Bursztynowski

Post by Radek Bursztynowski
Hello,
I have a problem with ending on server thin client LTSP session. When I log
out from the server session I return to the LDM, but there are not closed my
radek 10790 0.0 0.0 20040 680 ? S 13:22 0:00 dbus-launch
--sh-syntax --exit-with-session
radek 10791 0.0 0.0 21816 1236 ? Ss 13:22 0:00
/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
radek 10858 0.0 0.0 232924 6588 ? Ss 13:22 0:00
/usr/bin/seahorse-agent --variables
radek 10862 0.0 0.0 137360 2152 ? S 13:22 0:00 /usr/libexec/gvfsd
radek 10876 0.0 0.0 133864 5808 ? S 13:22 0:00 /usr/libexec/gconfd-2
radek 10906 0.0 0.0 24752 2032 ? S 13:22 0:00
/usr/lib64/xfce4/xfconf/xfconfd
radek 10929 0.0 0.0 238448 5640 ? S 13:22 0:00 Thunar --daemon
radek 10936 0.0 0.0 242892 2900 ? Ss 13:22 0:00 gnome-screensaver
radek 10943 0.0 0.0 328644 10784 ? Sl 13:22 0:00
/usr/libexec/polkit-gnome-authentication-agent-1
radek 10946 0.0 0.0 508884 10908 ? S 13:22 0:00
gnome-volume-control-applet
radek 10952 0.0 0.0 115096 4052 ? S 13:22 0:00
/usr/libexec/im-settings-daemon
radek 10975 0.0 0.0 251984 6792 ? S 13:22 0:00 gnome-power-manager
radek 10978 0.0 0.1 303344 18736 ? S 13:22 0:00 python
/usr/share/system-config-printer/applet.py
radek 10986 0.0 0.0 362372 9840 ? S 13:22 0:00 gpk-update-icon
radek 10997 0.0 0.0 358308 6872 ? S 13:22 0:00
/usr/libexec/evolution/2.32/evolution-alarm-notify
radek 11119 0.0 0.0 40900 2232 ? S 13:22 0:00
/usr/libexec/gconf-im-settings-daemon
radek 11120 0.0 0.0 201512 2528 ? S 13:22 0:00 xfsettingsd
radek 11140 0.0 0.0 148776 3532 ? S 13:22 0:00
/usr/libexec/gvfs-gdu-volume-monitor
radek 11144 0.0 0.0 232436 2064 ? Sl 13:22 0:00
/usr/libexec/gvfs-afc-volume-monitor
radek 11147 0.0 0.0 150892 2196 ? S 13:22 0:00
/usr/libexec/gvfs-gphoto2-volume-monitor
radek 11149 0.0 0.0 146304 3228 ? S 13:22 0:00
/usr/libexec/gvfsd-trash --spawner :1.2 /org/gtk/gvfs/exec_spaw/0
radek 11297 0.0 0.0 356628 10964 ? S 13:28 0:00
/usr/libexec/notification-daemon
radek 11832 0.0 0.0 20040 692 ? S 13:40 0:00 dbus-launch
--sh-syntax --exit-with-session
radek 11833 0.0 0.0 21668 1208 ? Ss 13:40 0:00
/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
radek 11900 0.0 0.0 235144 6708 ? Ss 13:40 0:00
/usr/bin/seahorse-agent --variables
radek 11908 0.0 0.0 137360 2104 ? S 13:40 0:00 /usr/libexec/gvfsd
radek 11914 0.0 0.0 133848 5768 ? S 13:40 0:00 /usr/libexec/gconfd-2
radek 12102 0.0 0.0 115096 4052 ? S 13:40 0:00
/usr/libexec/im-settings-daemon
radek 12258 0.0 0.0 40900 2232 ? S 13:40 0:00
/usr/libexec/gconf-im-settings-daemon
Could anybody advice me how to close all processes within log out?
Best regards,
Radek
_______________________________________________
K12OSN mailing list
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>

Radek Bursztynowski

2014-04-17 17:56:26 UTC

Permalink

Hello,

Many thanks for advice. I will test it tomorrow
.
Coming back to this problem with Fedora 11 thin client image I keep
conviction that I have to do something on thin client site. After
killing all user processes on server site I can see on thin client
working one user process (socket ***@server_ip_address. When I kill
this proces on the terminal LDM reloads and everything comes back to the
norm. So I must to do something with Fedora 11 thin client image.

Best regards,
Radek

Post by Radek Bursztynowski
Hello,
I have this same problem and I found the 'slay' command works
perfectly to resolve the leftover processes.
# slay username
Plus it's fun to tell the others that I had to 'slay' so-and-so :)
http://linuxpoison.blogspot.ca/2011/01/kills-all-of-users-processes-slay.html
Joseph
On Wed, Apr 16, 2014 at 7:50 AM, Radek Bursztynowski

_______________________________________________
K12OSN mailing list
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>

a***@smart.net

2014-04-17 18:47:18 UTC

Permalink

yes I had to do that a couple times but it gets old having to slay them
one at a time

Bob

Date: Thu, 17 Apr 2014 19:56:26 +0200
Subject: Re: [K12OSN] Log off doesn end all user processes
Hello,
Many thanks for advice. I will test it tomorrow
.
Coming back to this problem with Fedora 11 thin client image I keep
conviction that I have to do something on thin client site. After
killing all user processes on server site I can see on thin client
this proces on the terminal LDM reloads and everything comes back to the
norm. So I must to do something with Fedora 11 thin client image.
Best regards,
Radek

_______________________________________________
K12OSN mailing list
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>

Radek Bursztynowski

2014-04-18 15:56:13 UTC

Permalink

Hello,

Thanks again for advice, but unfortunately 'slay' doesn't solve my
problem with Fedora 11 thin client image. So, I should come back to my
previous idea - to do something with thin client image.

Best regards,
Radek

--

_______________________________________________
K12OSN mailing list
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>