Leendert Meyer wrote:
Moral: everybody can make a mistake as root. Better avoid being root. :P
Playing with initscripts: how much can you do without being root? 'FOO start' and 'FOO stop' probably work as a normal user (at least my example would). No need to do insserv to test the workings of that script. Need to be root? Use 'su FOO start', and type the password for root. That makes you think twice, hopefully. Or not. ;P I do agree with you, but there is some kind of thought that if I do something as a simple user, which requires root password, I will enter it(even after a second thought), otherwise you will never know that you shouldn't have done so...;)
(Can't remember putting '> /etc/inittab' or so in my example...)
there was no such a thing in your post, definetely, and neither I did something when was editing the one you post. By the way a little question about editing...I tried to write in FOO.log something like echo "$(date +%FT%T%z): FOO started by the user $USER" >> /tmp/FOO.log but it didn't get the value for $USER. and writes in file only "date: FOO started by user". Is it possible to get the user who starts FOO?
What does 'grep inittab /root/.bash_history' say?
I am also intrigued to check it, but unfortunately the problem got deeper, now I am not able to even login to Linux...at booting it says INIT: version 2.85 booting INIT: cannot execute "/etc/init.d/boot" INIT: Entering runlevel: 5 INIT: cannot execute "/etc/init.d/rc" (none) login: root(or any another user) login: PAM Failure, aborting: Critical error - immediate abort And booting at a Failsafe mode gives the same... It is already 03.30 night here and I still can't make it to work... -- Sergey Mkrtchyan Scientific Researcher Department of Molecular Physics, Faculty of Physics, Yerevan State University Tel: (374-10) 55-43-41 Fax: (374-10) 57-76-89