Hi *,
This past weekend, I believe someone did something to our system (I believe I know who, but since most E-mail is tracked, I'll not say here), but alas, I cannot confirm it. I have already change $HISTSIZE in hopes of tracking stuff like this in the past.
I have found that /etc, /usr and /dev all have 777 permissions. Who knows what else...I haven't found any more, but I haven't really looked either. This is a common repair this individual does. If something does not work, just do a chmod 777 *.
Anyway, now our print spooling system is hosed. It stops working after a while and if I do a stopsrc -g spooler, it does not shutdown. I end up doing kills on the processes.
So, this all said, does anyone know why the print spooler system might act like this ? Granted, this type of problem may have a billion (US) possible causes, but I am willing to chase them down.
Here is what I have done so far...
1. I wrote a script that lists files and their numeric permissions, colon delimited
2. Ran the script on a freshly installed system for each of the above directories
3. Wrote another script that reads the files and numeric permission and chmod's them on my quirky system
This seems to have fixed some of the problems we were having, but this print spooler one still exists.
Any thoughts ?
Thanks, Bill.
This past weekend, I believe someone did something to our system (I believe I know who, but since most E-mail is tracked, I'll not say here), but alas, I cannot confirm it. I have already change $HISTSIZE in hopes of tracking stuff like this in the past.
I have found that /etc, /usr and /dev all have 777 permissions. Who knows what else...I haven't found any more, but I haven't really looked either. This is a common repair this individual does. If something does not work, just do a chmod 777 *.
Anyway, now our print spooling system is hosed. It stops working after a while and if I do a stopsrc -g spooler, it does not shutdown. I end up doing kills on the processes.
So, this all said, does anyone know why the print spooler system might act like this ? Granted, this type of problem may have a billion (US) possible causes, but I am willing to chase them down.
Here is what I have done so far...
1. I wrote a script that lists files and their numeric permissions, colon delimited
2. Ran the script on a freshly installed system for each of the above directories
3. Wrote another script that reads the files and numeric permission and chmod's them on my quirky system
This seems to have fixed some of the problems we were having, but this print spooler one still exists.
Any thoughts ?
Thanks, Bill.