The tests you had listed : Single Parenthesis – ( … ) is creating a subshell Double Parenthesis – (( … )) is for arithmetic operation Single Square Bracket – [ … ] is the syntax for the POSIX test Double Square Brackets – [[ … ]] is the syntax for bash conditional expressions (similar … Read more
The characters ‘<‘, and ‘>’, are to indicate a place-holder, you should remove them to read: php /usr/local/solusvm/scripts/pass.php –type=admin –comm=change –username=ADMINUSERNAME
You need to source the file as: . myfile.sh or source myfile.sh Without sourcing the changes will happen in the sub-shell and not in the parent shell which is invoking the script. But when you source a file the lines in the file are executed as if they were typed at the command line.
ls -lR $dir > a ls -lR $dir > b DIFF=$(diff a b) if [ “$DIFF” != “” ] then echo “The directory was modified” fi
Chances are that on your desktop you are not actually running under bash but rather dash or some other POSIX-compliant shell that does not recognize the function keyword. The function keyword is a bashism, a bash extension. POSIX syntax does not use function and mandates the use of parenthesis. $ more a.sh #!/bin/sh function sayIt … Read more
Easiest solution and always latest version: run this curl in your gitbash: curl -L -o /usr/bin/jq.exe https://github.com/stedolan/jq/releases/latest/download/jq-win64.exe or manually save the jq-win64.exe in link above as jq.exe to your /usr/bin (which is in your git bash installation folder) (if you are behind a proxy add the -x proxyhost:port)
As suggested by Abel Muiño in comments, this may have been fixed in more recent Docker versions (I’m currently running 0.9.1). But, if you’re temporarily stuck like me with an older version, I did find a decent workaround to check if the container started by using docker inspect. docker inspect returns a JSON object with … Read more
Use $# which is equal to the number of arguments supplied, e.g.: if [ “$#” -ne 1 ] then echo “Usage: …” exit 1 fi Word of caution: Note that inside a function this will equal the number of arguments supplied to the function rather than the script. EDIT: As pointed out by SiegeX in … Read more
You are looking for -H option in gnu grep. find . -name ‘*bills*’ -exec grep -H “put” {} \; Here is the explanation -H, –with-filename Print the filename for each match.
I think I found the answer: In the .service file, I needed to add /bin/bash before the path to the script. For example, for backup.service: ExecStart=/bin/bash /home/user/.scripts/backup.sh As opposed to: ExecStart=/home/user/.scripts/backup.sh I’m not sure why. Perhaps fish. On the other hand, I have another script running for my email, and the service file seems to … Read more