There is no difference if you do not put $* or $@ in quotes. But if you put them inside quotes (which you should, as a general good practice), then $@ will pass your parameters as separate parameters, whereas $* will just pass all params as a single parameter. Take these scripts (foo.sh and bar.sh) … Read more
$? is a variable holding the return value of the last command you ran. Example C program (example.c): int main() { return 1; } Example Bash: gcc -o example example.c ./example echo $? # prints 1
I personally use Console2 with the Bash shipped with MYSYS-Git. You can also use PuTTY and SSH to a real linux box 😉
I ran into this same problem a few minutes ago. Looks like the classy folks behind Modernizr’s Rubygem yanked the most recent versions. You can download the latest gem (Modernizr-2.5.2 as required in the docs there) running the following command inside your /home/git/gitlab directory: wget http://rubygems.org/downloads/modernizr-2.6.2.gem Then, go ahead and run gem install modernizr (without … Read more
You can use easily: .find({ “_id” : CSUUID(“E3E45566-AFE4-A564-7876-AEFF6745FF”)})
You may need to escape the % with a \. % is a special character to the crontab, which gets translated to a newline, so your code was probably becoming -p’]T zw51′ Try: -p’]T\%zw51′
until is the opposite of while. It’s nothing to do with doing stuff while another command runs. For that you need to run your task in the background with &. cp SOURCE DEST & pid=$! # If this script is killed, kill the `cp’. trap “kill $pid 2> /dev/null” EXIT # While copy is running… … Read more
The shebang is only mandatory for those scripts which shall be executed by the operating system in the same way as binary executables. If you source in another script, then the shebang is ignored. On the other hand. IF a script is supposed to be sourced, then it is convention to NOT put any shebang … Read more
Sending a newline \n will exectue the command. .end() will exit the shell. I modified the example to work with bash as I’m on osx. var terminal = require(‘child_process’).spawn(‘bash’); terminal.stdout.on(‘data’, function (data) { console.log(‘stdout: ‘ + data); }); terminal.on(‘exit’, function (code) { console.log(‘child process exited with code ‘ + code); }); setTimeout(function() { console.log(‘Sending stdin … Read more
ssh is in fact just passing a string to the remote host. There this string is given to a shell which is supposed to interpret it (the user’s login shell, which is typically something like bash). So whatever you want to execute needs to be interpretable by that remote login shell, that’s the whole rule … Read more