03-27-2019
That code was suggested by someone.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
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)
Discussion started by: iago
1 Replies
2. 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
3. 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
4. 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
5. 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
6. 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
7. 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
8. 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
9. 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
10. 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
LEARN ABOUT FREEBSD
compile_et
COMPILE_ET(1) BSD General Commands Manual COMPILE_ET(1)
NAME
compile_et -- error table compiler
SYNOPSIS
compile_et file
DESCRIPTION
Compile_et converts a table listing error-code names and associated messages into a C source file suitable for use with the com_err(3)
library.
The source file name must end with a suffix of ``.et''; the file consists of a declaration supplying the name (up to four characters long) of
the error-code table:
error_table name
followed by up to 256 entries of the form:
error_code name, "string"
and a final
end
to indicate the end of the table.
The name of the table is used to construct the name of a subroutine initialize_XXXX_error_table which must be called in order for the
com_err(3) library to recognize the error table.
The various error codes defined are assigned sequentially increasing numbers (starting with a large number computed as a hash function of the
name of the table); thus for compatibility it is suggested that new codes be added only to the end of an existing table, and that no codes be
removed from tables.
The names defined in the table are placed into a C header file with preprocessor directives defining them as integer constants of up to 32
bits in magnitude.
A C source file is also generated which should be compiled and linked with the object files which reference these error codes; it contains
the text of the messages and the initialization subroutine. Both C files have names derived from that of the original source file, with the
``.et'' suffix replaced by ``.c'' and ``.h''.
A ``#'' in the source file is treated as a comment character, and all remaining text to the end of the source line will be ignored.
SEE ALSO
yacc(1), com_err(3)
Ken Raeburn, A Common Error Description Library for UNIX.
BUGS
Since compile_et uses a very simple parser based on yacc(1), its error recovery leaves much to be desired.
BSD
November 22, 1988 BSD