Ok so i had to create a file and put some random text into it which i did.
THen u make a script which takes 2 arguments.
The first being a line of text, the second being your newly created file.
The script should take the first argument and insert it into the very top (the first line) of... (1 Reply)
Hi Guys
I have this small Bash script - but it fails when I'm trying to run it.
./test.sh: && ; then
# date >> /writable/sys/shutdown.log
shutdown -h "now"
exit
fi
done (4 Replies)
I can't find anything wrong with this line of code, it works when there is one file in the directory but more than one i get a "too many arguements2 error
if ; then
am i missing something? (3 Replies)
i don't know what's wrong with the code, says too many arguments in the first two if statements. how to change it? thx.
the file is like in this format:
;dfs;dfdsf;fsd ff dsf;dfdffdfd; -f2 should be only one word with no space, but could be like this 'n/a', '**ABC'
while read line; do
... (1 Reply)
Hi Experts ,
I have following code
if ; then
mv path /filename newdirpath
echo "K* files moved successfully to newdirpath \n"
else
echo "K* files DID NOT moved successfully to newdirpath \n"
fi
I am getting
"echo "K* files DID NOT moved successfully to newdirpath \n"... (19 Replies)
I have a SNMP agent that sends three arguments to the script to get a value at the end. The first is the LeafNumber, second is the request type (SET, GET, GETNEXT), and the last is a string that represents some value to be set(used only for set requests).
The agent string looks like this:
... (3 Replies)
line 5: #!/bin/bash
old=$(du -sh /home/andy/Downloads/myfile.iso)
while true; do
new=$(du -sh /home/andy/Downloads/myfile.iso)
if ;
then
break
fi
old=$new
xdotool getactivewindow key Ctrl
sleep 5
done
line 5: bash - Meaning of " (square brackets)... (9 Replies)
Discussion started by: drew77
9 Replies
LEARN ABOUT DEBIAN
escape
escape(1) Mail Avenger 0.8.3 escape(1)NAME
escape - escape shell special characters in a string
SYNOPSIS
escape string
DESCRIPTION
escape prepends a "" character to all shell special characters in string, making it safe to compose a shell command with the result.
EXAMPLES
The following is a contrived example showing how one can unintentionally end up executing the contents of a string:
$ var='; echo gotcha!'
$ eval echo hi $var
hi
gotcha!
$
Using escape, one can avoid executing the contents of $var:
$ eval echo hi `escape "$var"`
hi ; echo gotcha!
$
A less contrived example is passing arguments to Mail Avenger bodytest commands containing possibly unsafe environment variables. For
example, you might write a hypothetical reject_bcc script to reject mail not explicitly addressed to the recipient:
#!/bin/sh
formail -x to -x cc -x resent-to -x resent-cc
| fgrep "$1" > /dev/null
&& exit 0
echo "<$1>.. address does not accept blind carbon copies"
exit 100
To invoke this script, passing it the recipient address as an argument, you would need to put the following in your Mail Avenger rcpt
script:
bodytest reject_bcc `escape "$RECIPIENT"`
SEE ALSO avenger(1),
The Mail Avenger home page: <http://www.mailavenger.org/>.
BUGS
escape is designed for the Bourne shell, which is what Mail Avenger scripts use. escape might or might not work with other shells.
AUTHOR
David Mazieres
Mail Avenger 0.8.3 2012-04-05 escape(1)