On Mon, Apr 21, 2008 at 12:13:16PM -0500, Charles Paul wrote:
> You also would want to send output to /dev/null because any
> stdout/stderr would make it very hard to work in the terminal you
> submitted this sort of thing.
> >
> > #!/bin/sh
> > connectssh-1.sh > /dev/null 2>&1 && \
> > connectssh-2.sh > /dev/null 2>&1 && \
> > connectssh-3.sh > /dev/null 2>&1 && \
> > connectssh-4.sh > /dev/null 2>&1 || echo oops, something screwed up
> > ##
>
> This would not be useful.
>
> LOGICAL AND would not do anything aside from running
> connectssh-1.sh... as these scripts do not fork, and an external kill
> signal would not satisfy the && conditional.
>
> Regardless, thanks for attempting to enhance my very quick example.
NP. My main point was that the first example was a bad practice and that there are many other issues to consider.
Brett
> ___________________
> Nolug mailing list
> nolug@nolug.org
___________________
Nolug mailing list
nolug@nolug.org
Received on 04/21/08
This archive was generated by hypermail 2.2.0 : 12/19/08 EST