Re: Rebooting woes ..was.. Rebooting is foolish ....

2001-02-17 Thread Sebastiaan
For my (little home) servers, I always try a reboot after I installed something regarding to the things it serves. If something goes wrong (power failure, accicent, etc) I know that the vital parts work directly 100% after reboot. As for my client/workstation system, I have to reboot when I need

Re: Rebooting woes ..was.. Rebooting is foolish ....

2001-02-17 Thread Dwayne C. Litzenberger
if it comes to it you can always go to runlevel 1 (init 1), when it prompts for the root password hit CTRL-D to come back to runlevel 2. that will effectivly restart all programs on the system except (i think) init, and of course the kernel. restarting programs really depends on the

Rebooting woes ..was.. Rebooting is foolish ....

2001-02-16 Thread SamBozo Debian User
Nate Amsden wrote: try avoid rebooting whenever possible. i had a bad experience with rebooting not too long ago. a sun ultra 10..up for about 130 days..shut it down to move a UPS, it never came back up. spent the next 15-20 hours rebuilding it. nate I Have had a simular experience

Re: Rebooting woes ..was.. Rebooting is foolish ....

2001-02-16 Thread Nate Amsden
SamBozo Debian User wrote: I KNOW THIS is NOT the proper way to do things with Linux ... but how else do you know? Please tell me? I'll change my evil ways... if it comes to it you can always go to runlevel 1 (init 1), when it prompts for the root password hit CTRL-D to come back to runlevel