08-22-2007
Arguments
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 the file named in your second argument.
ive got this so far
BUFF=$(cat $2) echo $1 >> $2 echo " $BUFF" >> $2
but im getting the wrong output when i cat the file i created 'heaney'
"Seamus Heaney was born in April 1939, the eldest member of a family which would eventually contain nine children.
unixisbrillant echo
i need to get the bottom line "unixisbrillant" at the top
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
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)
Discussion started by: tainted2real
4 Replies
2. Shell Programming and Scripting
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)
Discussion started by: Alendrin
3 Replies
3. Shell Programming and Scripting
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)
Discussion started by: dtdt
1 Replies
4. Shell Programming and Scripting
hi
I am getting too many arguments error for the below line
if ; then
Thx in advance (1 Reply)
Discussion started by: vls1210
1 Replies
5. Shell Programming and Scripting
echo "the number from 1 to 10:"
i=1
while
do
echo $i
i=`expr $i+1'
done
above is the program i written in Linux O.S using vi editor
but i am getting the error that
while: line 3:
i am not understanding that why i am getting this error.
can any body please help me regarding this... (3 Replies)
Discussion started by: bsatishbabu
3 Replies
6. Shell Programming and Scripting
Hello,
is it possible to give grep two documents to surche for? like
grep "test" /home/one.txt AND /home/two.txt ?
thanks (1 Reply)
Discussion started by: Cybertron
1 Replies
7. Shell Programming and Scripting
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)
Discussion started by: ajaypatil_am
19 Replies
8. Shell Programming and Scripting
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)
Discussion started by: jsoper1
3 Replies
9. Shell Programming and Scripting
hi I have this code
a="a b c"
set -- $a
if ; then
echo empty
fi
why is it line 3 reports "test: [: too many arguments"? :wall:
Thanks! (4 Replies)
Discussion started by: h0ujun
4 Replies
10. Ubuntu
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 OPENDARWIN
shlock
SHLOCK(1) BSD General Commands Manual SHLOCK(1)
NAME
shlock -- create or verify a lock file for shell scripts
SYNOPSIS
shlock -f lockfile [-p PID] [-u] [-v]
DESCRIPTION
The shlock command can create or verify a lock file on behalf of a shell or other script program. When it attempts to create a lock file, if
one already exists, shlock verifies that it is or is not valid. If valid, shlock will exit with a non-zero exit code. If invalid, shlock
will remove the lock file, and create a new one.
shlock uses the rename(2) system call to make the final target lock file, which is an atomic operation (i.e. "dot locking", so named for this
mechanism's original use for locking system mailboxes). It puts the process ID ("PID") from the command line into the requested lock file.
shlock verifies that an extant lock file is still valid by using kill(2) with a zero signal to check for the existence of the process that
holds the lock.
The -f argument with lockfile is always required.
The -p option with PID is given when the program is to create a lock file; when absent, shlock will simply check for the validity of the lock
file.
The -u option causes shlock to read and write the PID as a binary pid_t, instead of as ASCII, to be compatible with the locks created by
UUCP.
The -v option causes shlock to be verbose about what it is doing.
RETURN VALUES
A zero exit code indicates a valid lock file.
EXAMPLES
BOURNE SHELL
#!/bin/sh
lckfile=/tmp/foo.lock
if shlock -f ${lckfile} -p $$
then
# do what required the lock
rm ${lckfile}
else
echo Lock ${lckfile} already held by `cat ${lckfile}`
fi
C SHELL
#!/bin/csh -f
set lckfile=/tmp/foo.lock
shlock -f ${lckfile} -p $$
if ($status == 0) then
# do what required the lock
rm ${lckfile}
else
echo Lock ${lckfile} already held by `cat ${lckfile}`
endif
The examples assume that the filesystem where the lock file is to be created is writeable by the user, and has space available.
HISTORY
shlock was written for the first Network News Transfer Protocol (NNTP) software distribution, released in March 1986. The algorithm was sug-
gested by Peter Honeyman, from work he did on HoneyDanBer UUCP.
AUTHOR
Erik E. Fair <fair@clock.org>
BUGS
Does not work on NFS or other network filesystem on different systems because the disparate systems have disjoint PID spaces.
Cannot handle the case where a lock file was not deleted, the process that created it has exited, and the system has created a new process
with the same PID as in the dead lock file. The lock file will appear to be valid even though the process is unrelated to the one that cre-
ated the lock in the first place. Always remove your lock files after you're done.
BSD
June 29, 1997 BSD