At 04:37 PM 3/15/01 -0300, you wrote:
> chown -R 755 * as root Does chown do this? Or did you mean chmod? This isn't clear; what exactly happened? a) everything now belongs to root with its old permissions b) everything still belongs to the right owner but is 755 c) everything now belongs to root *and* is 755 Also, where exactly were you when you did this? What server are you running? What patches are installed? How many times did they hit you on the head? (Just kidding.) -- Rodolfo J. Paiz rpaiz@xxxxxxxxxxxxxx <mailto:rpaiz@xxxxxxxxxxxxxx>
I believe he meant to do chmod, but did chown instead. Now all his files are owned by 755.
Possibly the reason that services are not working is that he doesn't have a user 755 on his system.
The mail spool files are in /home/spool/mail. They should be owned by their respective users. I don't know off-hand how to fix all Chris' problems, but it sounds as though he is going to get very used to typing "chown" in the near future (or restoring from a backup).
Chris, you can log onto your POP server because the users and their associated passwords have not been changed. You are able to get to some sites (like the admin interface), apparently because the system does not care who owns the files that make up the site. It may be that some daemons are not starting up properly because components do need to have ownership by a certain "user" (root, httpd, etc.).
Peter