Search Results

BTW, the bash-3 builtin test or [ ] has a buggy implementation (fixed in bash-4):
test -w and test -r call stat() rather than access(). That goes wrong
- if a file appears writable but the file...

Man pages in general are not tied to a particular shell. You should defer to the set of man pages for your particular version of unix. Like aix, solaris, etc.

man pages are independent from the shell so you'll see the same info regardless of the one you use (assuming you have the same version of the manuals, of course). Some distributions pack all the man...

Many enhancements have been made to ksh93, over the years. If you use the same version of ksh93 on all platforms (ksh --version will tell you) you should not have compatibility problems on different...

I remember the times when you were taught shell basics, and so was pure sh for compatibility, it is also true for ksh... things may change when it comes to advanced features and extensions where it...

I don't know exactly why bash came up, since your question is about ksh. On Linux (if ksh is installed) this is typically a recent version of ksh93 which supports the =~ syntax, whereas on many UNIX...

=~ is BASH-only syntax, and only very new versions of BASH at that.

Most shells will let you do if [[ "$instance" == *DEV* ]] however.

I'd rather write the PID of your cronscript to that tempfile, so you can check right away if the process is still running or not, by matching ps $(cat tempfile).

So in your cron script you do...

Might want to log stderr as well:
ssh -T $PROXY_USER@$PROXY_SERVER < script.txt > ssh_output.log 2> ssh_error.log

or
ssh -T $PROXY_USER@$PROXY_SERVER < script.txt > ssh_output.log 2>&1

It's ok.