How do I kill all a user's processes using their UID
Solution 1
Use pkill -U UID
or pkill -u UID
or username instead of UID. Sometimes skill -u USERNAME
may work, another tool is killall -u USERNAME
.
Skill was a linux-specific and is now outdated, and pkill is more portable (Linux, Solaris, BSD).
pkill allow both numberic and symbolic UIDs, effective and real http://man7.org/linux/man-pages/man1/pkill.1.html
pkill - ... signal processes based on name and other attributes
-u, --euid euid,... Only match processes whose effective user ID is listed. Either the numerical or symbolical value may be used. -U, --uid uid,... Only match processes whose real user ID is listed. Either the numerical or symbolical value may be used.
Man page of skill says is it allowed only to use username, not user id: http://man7.org/linux/man-pages/man1/skill.1.html
skill, snice ... These tools are obsolete and unportable. The command syntax is poorly defined. Consider using the killall, pkill
-u, --user user The next expression is a username.
killall is not marked as outdated in Linux, but it also will not work with numberic UID; only username: http://man7.org/linux/man-pages/man1/killall.1.html
killall - kill processes by name
-u, --user Kill only processes the specified user owns. Command names are optional.
I think, any utility used to find process in Linux/Solaris style /proc (procfs) will use full list of processes (doing some readdir of /proc
). I think, they will iterate over /proc
digital subfolders and check every found process for match.
To get list of users, use getpwent
(it will get one user per call).
skill (procps & procps-ng) and killall (psmisc) tools both uses getpwnam
library call to parse argument of -u
option, and only username will be parsed. pkill
(procps & procps-ng) uses both atol and getpwnam to parse -u
/-U
argument and allow both numeric and textual user specifier.
Solution 2
If you pass -1 as the process ID argument to either the kill
shell command or the kill
C function, then the signal is sent to all the processes it can reach, which in practice means all the processes of the user running the kill
command or syscall.
su -c 'kill -TERM -1' bob
In C (error checking omitted):
if (fork() == 0) {
setuid(uid);
signal(SIGTERM, SIG_DFL);
kill(-1, SIGTERM);
}
Solution 3
If the pkill function is unavailable on your UNIX / Linux distribution you could run the following command as the root user:
ps -ef | grep username | grep -v grep | awk '{print $2}' | xargs kill
where username is the user who's processes you want to delete
Solution 4
pgrep -U username|xargs kill -9
Related videos on Youtube
user489152
Updated on September 18, 2022Comments
-
user489152 almost 2 years
I want to kill all running processes of a particular user from either a shell script or native code on a Linux system.
Do I have to read the /proc directory and look for these?
Any ideas? Is there a dynamic mapping of the pids under UIDs in Linux? Isn't this in the proc?
If not, then where is this list maintained? Should I read from it? Also where is the static list of all UIDs in the system so I can validate this this user exists and then proceed to kill all processes running under it?
-
Admin almost 13 yearsDo you want a tool to do this (pkill, slay, others exist), or do you want to write it yourself? If the former, the superuser stack exchange site is probably better. If the latter, scanning /proc and making a note for all processes by a specific user is the way to go. The source code for the pkill utility would, for example, show how to do that.
-
tcoolspy almost 13 yearsCould you clarify what this question was about in light of @LarsWirzenius's comment? Thanks!
-
user489152 almost 13 years@Caleb: I wanted to kill processes by reading the /proc as I didn't know of any tool doing it. Also now I find that other than "kill", "pkill", "skill" etc are not available on my system. In that case I guess I have to look at shell script alternatives to read the /proc and figure out a way to get processes under one user. Any ideas?
-
Gilles 'SO- stop being evil' almost 13 yearsRegarding “the static list of all UIDs … so I can validate this this user exists”: there is no such thing as validating a user ID. User names come from a database, but user IDs are whatever a process running
setuid()
chooses.
-
-
Admin almost 13 yearspkill is not obsolete. It may be unportable outside Linux, but the question was about Linux specifically.
-
Petesh almost 13 yearsto get the list of users use the one liner: getent passwd | awk -F: '{print $1}'
-
Arsen Ghazaryan almost 13 yearsYes, you can. Not a kill, but
pkill -u UID -##
, where UID is number user id and##
is signal number. -
Arsen Ghazaryan almost 13 yearsor just the
pkill -U username
. -
user489152 almost 13 years@osgx: Sadly, kill is the only utility I have :(
-
Arsen Ghazaryan almost 13 yearsis it an embedded linux? you have no skill, pkill and killall? Even busybox embedded shell has pkill and killall.
-
michalzuber about 9 years
killall -u USERNAME
worked like charm -
Laurence Cope about 7 yearshas skill changed now, as my skill expects a username with the -u flag, not the user ID: -u The next argument is a username.
-
Arsen Ghazaryan about 7 years@LaurenceCope, Thanks, I updated the answer. No, skill of procps-ng was not changed, only text username for
skill -u username
is allowed. Tool usesgetpwnam
libcall (it is defined only for user name, not for id) to parse-u
argument for more than 5 years gitlab.com/procps-ng/procps/blame/master/skill.ccase 'u': .... passwd_data = getpwnam(optarg);
Same for skill in classic procps: procps.cvs.sourceforge.net/viewvc/procps/procps/…. -
RoboAlex over 4 years
skill -u username
saved my day -
Kusalananda over 4 yearsIf you have
pgrep
you also havepkill
. Why not use it? -
Kusalananda over 4 yearsWhy the last step with
usermod
? -
Saddam ZEMMALI over 4 yearsmodify a user's account
-
Kusalananda over 4 yearsYou don't have to use
usermod
to kill a user's processes. Please explain that step further and why you think it's necessary. -
famzah almost 4 yearsThis is the best solution.
kill -1
avoids any race-conditions but please read the following article for additional information: lwn.net/Articles/754980 -
Arsen Karapetjan about 3 yearsis there one that doesn't kill my ssh connection to the server I'm connected to?
pkill -U user
kills me and logs me out.