06-19-2008
More generally, the test command (aka opening square bracket [ command) has a number of operators for checking file permissions. test -w file checks if you have write access, test -d file checks if it's a directory, etc.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi guys and Gals AIX 5.1
If I had a # above several scripts would it comment out everything below it?
Like this
#
01 2 ** .....................................
02 31 .........................................
# this is a script
03 12 **..........................
Would... (6 Replies)
Discussion started by: rocker40
6 Replies
2. Shell Programming and Scripting
SCO 5.06
Is there a variable that holds a user's comment?
In scoadmin -account, there's a comment field which we normally
populate with the user's name.
Or ... am I better off greping /etc/passwd?
Thanks! (2 Replies)
Discussion started by: gseyforth
2 Replies
3. Shell Programming and Scripting
Hi guys, hope you scripting gurus here can help me out, the logic in my script somehow not working the way it should, this script part of a bigger backup script suppose to do some checking on the cluster prior to bringing up the package on MC/SG after backend cloning operation, this portion is... (3 Replies)
Discussion started by: sparcguy
3 Replies
4. Shell Programming and Scripting
Hi,
My requirement is to comment/uncomment a cron job through a script.
1. Redirected the output of crontab -l to a text file.
crontab -l >cronoutput.txt
2. grep to find the script running and sed to place the comment (#) as
the first char
grep -i 'weblogicmonitor.sh'... (5 Replies)
Discussion started by: mannepalli
5 Replies
5. UNIX for Dummies Questions & Answers
Is there a command to put a comment (#) in a whole part of a shell script? (5 Replies)
Discussion started by: vero_81
5 Replies
6. Shell Programming and Scripting
I want to comment 2 lines based on a condition. If THEN occurs immediately after WHEN then i have to comment both the lunes
For example :
$cat file1.txt
CASE
WHEN
THEN 1
WHEN
c1= 'I'
AND c2= '0'
THEN 2
So in this example i want to... (2 Replies)
Discussion started by: ashwin3086
2 Replies
7. Shell Programming and Scripting
Hi,
I am writing a shell script, which should comment a if-fi loop in a file.
From google i found that, we can use below qualifier to comment a section of code,
:<<COMMENT
COMMENT
But i could not place these keywords before and after if-fi loop.
Any help would be appreciated.
Finally the... (2 Replies)
Discussion started by: successlin
2 Replies
8. Web Development
I have set the sh file to chmod 755
i only able to print the output but cannot execute the copy why?
Below is the code for sh file
echo "Hello"
cp hello.sh helloworld.sh
Below is my code for php.
<html>
<head>
</head>
<body>
<?php echo '<p>Hello</>'; ?>
<?php shell_exec('sh... (4 Replies)
Discussion started by: zhengkoon8
4 Replies
9. Shell Programming and Scripting
I need to insert a comment string to a couple of fields for every line in the file. Different comment string for each field.
In below file, fields 7 and 8
"R","1","t0000684","","10/31/2013","10/31/2013","","","","750.23"... (6 Replies)
Discussion started by: Melah Gindi
6 Replies
10. Shell Programming and Scripting
Hello,
I have a file, in which line 40 is commented. It is basically a cron job,
#05,35,50 * * * * /usr/local/scripts/my.sh
how i can i verify the line 40 is commented, if not then give me message not commented, otherwise provide us message it is commented. (5 Replies)
Discussion started by: learnbash
5 Replies
test(1F) FMLI Commands test(1F)
NAME
test - condition evaluation command
SYNOPSIS
test expression
expression
DESCRIPTION
test evaluates the expression expression and if its value is true, sets a 0 (TRUE) exit status; otherwise, a non-zero (FALSE) exit status
is set; test also sets a non-zero exit status if there are no arguments. When permissions are tested, the effective user ID of the process
is used.
All operators, flags, and brackets (brackets used as shown in the second SYNOPSIS line) must be separate arguments to test. Normally these
items are separated by spaces.
USAGE
Primitives
The following primitives are used to construct expression:
-r filename True if filename exists and is readable.
-w filename True if filename exists and is writable.
-x filename True if filename exists and is executable.
-f filename True if filename exists and is a regular file.
-d filename True if filename exists and is a directory.
-c filename True if filename exists and is a character special file.
-b filename True if filename exists and is a block special file.
-p filename True if filename exists and is a named pipe (FIFO).
-u filename True if filename exists and its set-user-ID bit is set.
-g filename True if filename exists and its set-group-ID bit is set.
-k filename True if filename exists and its sticky bit is set.
-s filename True if filename exists and has a size greater than 0.
-t[fildes] True if the open file whose file descriptor number is fildes (1 by default) is associated with a terminal
device.
-z s1 True if the length of string s1 is 0.
-n s1 True if the length of the string s1 is non-zero.
s1 = s2 True if strings s1 and s2 are identical.
s1 != s2 True if strings s1 and s2 are not identical.
s1 True if s1 is not the null string.
n1 -eq n2 True if the integers n1 and n2 are algebraically equal. Any of the comparisons -ne, -gt, -ge, -lt, and -le
may be used in place of -eq.
Operators
These primaries may be combined with the following operators:
! Unary negation operator.
-a Binary and operator.
-o Binary or operator (-a has higher precedence than -o).
`(expression)` Parentheses for grouping. Notice also that parentheses are meaningful to the shell and, therefore,
must be quoted.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
find(1), sh(1), attributes(5)
NOTES
If you test a file you own (the -r , -w , or -x tests), but the permission tested does not have the owner bit set, a non-zero (false) exit
status will be returned even though the file may have the group or other bit set for that permission. The correct exit status will be set
if you are super-user.
The = and != operators have a higher precedence than the -r through -n operators, and = and != always expect arguments; therefore, = and !=
cannot be used with the -r through -n operators.
If more than one argument follows the -r through -n operators, only the first argument is examined; the others are ignored, unless a -a or
a -o is the second argument.
SunOS 5.10 5 Jul 1990 test(1F)