When to trust compound statements and when to test? was: restart all services?
On Sat, 08 Jun 2002 15:07:10 -0700, Karsten M. Self wrote:
<snip>
>
>If you can bounce the system, issue a shutdown to maintenance, and then
>back up to full services. That's not a system restart, but rather stops
>all user and daemon processes, then restarts them.
>
>If that's too drastic:
>
> $ for file in /etc/rc2.d/S*; do $file stop; $file start; done
Is there a rule of thumb to determine when sequential commands should be
trusted and when they should be tested? In the above example, if the
stop command does not exit 0, is any harm done by going into the start
command? What should I look for that would suggest the need for
testing; eg., "do $file stop && $file start;" The possibility exists
(citing extreme shell ignorance) that I'm totally off base even bringing
up the question.
--
gt
It is interesting to note that as one evil empire (generic) fell,
another Evil Empire (tm) began its nefarious rise. -- me
Coincidence? I think not.
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: