10-03-2017
Hi,
test -s checks if the file exists and its size is greater than zero.
So if the file exists but is empty it will be removed.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello all,
I'm hoping to get a little insight from some of the wily veterans amongst you.
I've written a script to check for new outgoing files to our vendors located on our ssl server. It seems to be working ok, but the final question here, will be one of logic, and/or a better way to... (4 Replies)
Discussion started by: mph
4 Replies
2. Shell Programming and Scripting
how does below tr command replace nonletters with newlines?
I think I understand tr -cs '\n' part.. but what is
A-Za-z\' <--- what is this??
tr -cs A-Za-z\' '\n' |
-c --complement
-s, --squeeze-repeats
replace each input sequence of a repeated character that is... (0 Replies)
Discussion started by: convenientstore
0 Replies
3. Shell Programming and Scripting
how does below tr command replace nonletters with newlines?
I think I understand tr -cs '\n' part.. but what is
A-Za-z\' <--- what is this??
tr -cs A-Za-z\' '\n' |
-c --complement
-s, --squeeze-repeats
replace each input sequence of a repeated character that is... (1 Reply)
Discussion started by: convenientstore
1 Replies
4. UNIX for Advanced & Expert Users
Hi
Our problem is knowing:
What is the "best" way of simulating a TRAP for ERR within a function, since we know this will not work directly with ksh93 and aix5. How can we save the error encountered in the function and then deal with it in the calling script?
Thanks! (3 Replies)
Discussion started by: theteeth07
3 Replies
5. UNIX and Linux Applications
Hi am having a c pgm. It has the include files (unistd.h,sys/types.h,win.h,scr.h,curses.h,stdarg.h and color.h). I don't know the purpose of these include files. will u plz explain me. (1 Reply)
Discussion started by: Mari.kb
1 Replies
6. Shell Programming and Scripting
I have a script
#!/bin/ksh
trap cleanup 20
cleanup()
{
cat $t.log
echo Caught
exit 1
}
if ;then
echo Found >>t.log
exit 20
else
echo Not found >>t.log
exit 20
fi (5 Replies)
Discussion started by: thana
5 Replies
7. Shell Programming and Scripting
Hi folks,
I have tried to add some trap detection in the below script....this script is used to monitor database activities...in a rather awkward way :rolleyes:....
The idea behind adding trap is that....this script creates lots of temporary files in the running folder to store the count... (1 Reply)
Discussion started by: frozensmilz
1 Replies
8. UNIX for Dummies Questions & Answers
Its great someone provided this script that strips out a filename and extension but can someone explain how each line works?
file1='Jane Mid Doe.txt'
newfile='Jane.txt'
1) ext=${file1##*.}
2) filename=${file%%.???}
3) set -- $filename
4) newfile="1.$extension" (1 Reply)
Discussion started by: Lillyt
1 Replies
9. Homework & Coursework Questions
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
That is the last reply I received from my instructor, and I'm looking for some alternatives.
When using... (2 Replies)
Discussion started by: newuser45
2 Replies
10. Shell Programming and Scripting
Hi,
I need more explination on it, how it works
abcd="$(echo "$abcd" | sed 's/ //g')" >> ${LOGFILE} 2>&1
can any one suggest me on this?
Rgds,
LKR (1 Reply)
Discussion started by: lakshmanraok
1 Replies
TEST(1) General Commands Manual TEST(1)
NAME
test - condition evaluation utility
SYNOPSIS
test expression
DESCRIPTION
The test utility evaluates the expression and, if it evaluates to true, returns a zero (true) exit status; otherwise it returns 1 (false).
If there is no expression, test also returns 1 (false).
All operators and flags are separate arguments to the test utility.
The following primaries are used to construct expression:
-b file
True if file exists and is a block special file.
-c file
True if file exists and is a character special file.
-d file
True if file exists and is a directory.
-e file
True if file exists (regardless of type).
-f file
True if file exists and is a regular file.
-g file
True if file exists and its set group ID flag is set.
-h file
True if file exists and is a symbolic link.
-n string
True if the length of string is nonzero.
-p file
True if file is a named pipe
-r file
True if file exists and is readable.
-s file
True if file exists and has a size greater than zero.
-t [file_descriptor]
True if the file whose file descriptor number is file_descriptor (default 1) is open and is associated with a terminal.
-u file
True if file exists and its set user ID flag is set.
-w file
True if file exists and is writable. True indicates only that the write flag is on. The file is not writable on a read-only file
system even if this test indicates true.
-x file
True if file exists and is executable. True indicates only that the execute flag is on. If file is a directory, true indicates
that file can be searched.
-z string
True if the length of string is zero.
string
True if string is not the null string.
s1 = s2
True if the strings s1 and s2 are identical.
s1 != s2
True if the strings s1 and s2 are not identical.
n1 -eq n2
True if the integers n1 and n2 are algebraically equal.
n1 -ne n2
True if the integers n1 and n2 are not algebraically equal.
n1 -gt n2
True if the integer n1 is algebraically greater than the integer n2 .
n1 -ge n2
True if the integer n1 is algebraically greater than or equal to the integer n2 .
n1 -lt n2
True if the integer n1 is algebraically less than the integer n2 .
n1 -le n2
True if the integer n1 is algebraically less than or equal to the integer n2 .
These primaries can be combined with the following operators:
! expression
True if expression is false.
expression1 -a expression2
True if both expression1 and expression2 are true.
expression1 -o expression2
True if either expression1 or expression2 are true.
(expression)
True if expression is true.
The
-a operator has higher precedence than the -o operator.
GRAMMAR AMBIGUITY
The test grammar is inherently ambiguous. In order to assure a degree of consistency, the cases described in the IEEE Std 1003.2
("POSIX"), section D11.2/4.62.4, standard are evaluated consistently according to the rules specified in the standards document. All other
cases are subject to the ambiguity in the command semantics.
RETURN VALUES
The test utility exits with one of the following values:
0 expression evaluated to true.
1 expression evaluated to false or expression was missing.
>1 An error occurred.
BUGS
Named pipes are not implemented in 2.11BSD.
STANDARDS
The test function is expected to be IEEE Std 1003.2 ("POSIX") compatible.
7th Edition March 13, 1995 TEST(1)