Search Results

Use a case statement to weed out the exceptions, like this: for f in ${PROJECT}; do case "$f" in *[tsa]_1*) continue;; esac # ... actual work here ... done

You're actually more likely to find /usr/bin/perl on a randomly selected Unix than you are bash. …

Bash is not universal (and if you don't need universal, why are you writing a shell script?) #! …

There have been several attempts to standardize the meanings of process exit codes. In addition to the one you mention, I know of: the BSDs have sysexits.h which defines meanings for values from 64 …

Bash) then you can assume an interpreter for a better scripting language is installed. Perl, for instance, is more likely to be available than Bash is. Therefore, you should never write a #! … /bin/bash script, because if that's an option, a better language is also an option. 1 For instance, Solaris 10 and older shipped the original Bourne shell as /bin/sh. …

The legacy /bin/sh is the only thing you can be certain you have, but Perl for instance is more likely to be available cross-platform than Bash. …

/bin/sh, because Bash is not guaranteed to be installed anywhere, let alone in /bin. It's actually much, much worse than that. … The basic Perl interpreter is more likely to be available than Bash. …

You are assuming that the output of who | grep jeevansai will be a single line, which is wrong. ++ who ++ grep jeevansai ++ cut -c 32-34 + ld='31 31 ' This is telling you that the command ld=`wh …

Supporting what the other answers have said, I looked up the code that invokes commands on the remote, https://github.com/openssh/openssh-portable/blob/4f29309c4cb19bcb1774931db84cacc414f17d29/session …