TIP: Click on subject to list as thread! ANSI
echo: linux
to: WILFRED VAN VELZEN
from: DAMON A. GETSMAN
date: 2015-06-14 21:39:00
subject: Re: Shell script issue; r

  Re: Re: Shell script issue; rsync error wtf
  By: Wilfred van Velzen to Khelair on Sat Jun 13 2015 12:00:20

 WV> What shell is /bin/sh on your system? Have you tried explicitly setting
 WV> #!/bin/bash for instance?

  I have not.  I'm not sure what exactly /bin/sh is on this system.  It's
CentOS, so whatever that's commonly using...  I normally default to /bin/sh
instead of bash or something of the sort because I'm used to catering to
environments where /bin/sh exists in /bin but bash lives in /usr/local/bin or
/usr/bin or something of the sort.  Vestigial urges to keep my stuff working in
the most minimal environment possible, I guess.

 WV> As port 22 is the default ssh port, you don't have to specify it. You can
 WV> just do -e ssh without the hassel of the quotes, for testing.

  That's true.  Had those things pointed out a few days ago to me by someone
else that looked over the script in person here.  Oopsie.

 WV> I do however always use -e 'ssh -o BatchMode=yes' ... YMMV ...

  I suppose I'll have to break out the man page and take a look to find out
what exactly that changes behaviorally now.  :)

  -D
--- SBBSecho 2.27-OpenBSD
* Origin: Tinfoil.synchro.net - now at FTN (1:340/200) (1:340/200)

SOURCE: echomail via QWK@docsplace.org

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.