Re: killing all processes of one user reliably



In comp.os.linux.security Tomasz Noi?ski <noix@xxxxxxxxx>:
On Wed, 31 Jan 2007 19:24:10 +0100 Michael Heiming wrote:

In comp.os.linux.security Tomasz Noi?ski <noix@xxxxxxxxx>:
Hi,

I've been researching ways to kill all processes of one user (while being
root, of course) and I couldn't find _one_ program doing it without race
conditions.

man fuser

Hint:
Go for the tty to get rid of the dude...

It is similar to "skill" (loops through /proc) and has the same race
condition. Therefore, it is _unreliable_.

It seems from your URL you have created an app that does solve
your problem, I have never run into.

You could just incorporate it into 'kill' and send the maintainer
a patch.

Good luck

--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo zvpunry@xxxxxxxxxx | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 301: appears to be a Slow/Narrow SCSI-0 Interface
problem
.



Relevant Pages

  • Re: killing all processes of one user reliably
    ... root, of course) and I couldn't find _one_ program doing it without race ... man fuser ... Go for the tty to get rid of the dude... ...
    (comp.os.linux.security)
  • Re: killing all processes of one user reliably
    ... man fuser ... Go for the tty to get rid of the dude... ... It is similar to "skill" and has the same race ...
    (comp.os.linux.security)
  • [PATCH] tty races
    ... There are a couple of tty race conditions, ... atomicity was previously guarded by the BKL. ... The second race is tty_open vs. tty_open. ... int open_fail_num; ...
    (Linux-Kernel)
  • Re: [kde-linux] [Bulk] Konsole Immunity Lost
    ... I really do not want them as they make the console almost unusable. ... So how do I get rid of them? ... You can see what your system is currently set at with (as root): ... Does not explain why I never got them before in konsole/yakuake. ...
    (KDE)
  • Re: securetty
    ... > Being the syatem administrator and somewhat remote from the console - ... > the tty addresses are variable,and thus I cannot set up a unique tty in ... need to be able to identify who did what as root. ...
    (comp.sys.hp.hpux)