Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm running a webserver at slicehost and decided to delete unused/unnecessary users. But I really don't know which ones are necessary for the system to work

I use it as apache webserver with mysql, php, memcached, ssh and proftpd.

This is the list of users in /etc/passwd.
How can I decide which ones to delete?

list:x:38:38:Mailing List Manager:/var/list:/bin/sh
gnats:x:41:41:Gnats Bug-Reporting System (admin):/var/lib/gnats:/bin/sh
mysql:x:102:105:MySQL Server,,,:/var/lib/mysql:/bin/false
logcheck:x:105:107:logcheck system account,,,:/var/lib/logcheck:/bin/false
share|improve this question

Here's what the debian documentation has to say about the matter:

share|improve this answer

Manually created users end up with a uid just above 1000 (unless you specified the uid). Just don't touch any other users than those in the 1000+ range manually.

Some accounts in the 100+ range are users linked to the programs you're running (Apache, MySQL, ProFTPd). In generaly, you should let packages deal with these users and not try to manage them manually.

share|improve this answer

It's hard to say, all the users are there because daemons and cron jobs needs it.

But I can tell you which ones you can't delete.

Make a top, a ps -aux or something like that, and check the users; if there's a process started by "nobody" user you can't delete it. If you feel that those processes shouldn't be there, then stop the daemons and uninstall its packages, and then delete the users.

Also check crontab and cron.d if you delete a user needed for start a cron job, that job never will work again.

For other users used as administrative users you can set its shell to /bin/false if you are unsure about to delete it. The user will remain there but nobody will get a shell from it

share|improve this answer
Let's say I set the shell to /bin/false to every user BUT the one I actually use. Will I break everything? – The Disintegrator Aug 28 '10 at 9:25
Always leave shell for your user and root user. for other users, again, depends on your configuration. There's no rule of thumb.The other users may need it or not. For example www-data on most cases, does not need a shell, but some cgi could need it. Historically all users under id 99 had a /bin/sh as login shells, these are historic or legacy users, all "modern" linux services already come configured to "/bin/false" (mysql, ftpd ... ) In general as pointed by Raphink, it's safe trust the package mantainers, if you can't you should dig in your sistem to know what each user does there. – theist Aug 30 '10 at 6:21

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.