Is there a way for a bash script to test if it can cd into a directory without actually attempting to cd into it?
I am looking for something along the lines of:
Code:
if [ -d $dir ];then
#code to execute
fi
except in this case I don't want to test if the directory exists; what I want is to test if the script has the permission to cd into the directory.
I know there are other ways of achieving this but does bash provide a shortcut?
Hello,
I'm trying to test if a directory specified in a script parameter is available or not.
I wrote a little code to do so, but there's a problem because I receive an error message.
My code:
#Verify command parameter
if
then
echo 'Incorrect command parameter'
echo... (3 Replies)
I've been using the following code to make sure a shell script only runs under a "safe" directory.
Comments/Improvements?
#!/bin/sh
#----------------------------------------------------------------------------#
#..........................................................#... (8 Replies)
i am using solaris 5.10. i can create two different files "test" and ".test" in the same directory. now suppose i want to change the attribute of the hidden file .test to visible is it possible???
since "." is just an attribute to mark a file hidden why is unix allows creation of "file" and... (14 Replies)
Hi,
I'm writing a shell script that will create a folder if it does not exist yet. Here's the script: (this if statement is inside a while loop)
folderName="Pics"
if ! test -d folderName
then
mkdir $folderName
fi
However, after the folder Pics has been created, every time the... (3 Replies)
rm: Unable to remove directory /mnt/users/test/logs/: File exists
ls -latr
total 191208
drwxrwxrwx 6 test echo 4096 Jul 3 22:36 ..
-rwxrwxrwx 1 test echo 97692804 Jul 3 22:36 .nfsDFA4
drwxrwxr-x 2 test echo 4096 Jul 3 23:00 .
M not able to delete... (4 Replies)
I'm almost pulling out my hair trying to figure out what's wrong with this... there's no reason I can see that it shouldn't be working. It seems that the code acts as though the conditional statement is true no matter what - I've even tried removing the negation operator, but it always goes into... (5 Replies)
This is the code:
while test 1 -eq 1
do
read a
$a
if test $a = stop
then
break
fi
done
I read a command on every loop an execute it.
I check if the string equals the word stop to end the loop,but it say that I gave too many arguments to test.
For example echo hello.
Now the... (1 Reply)
How to check weather a string is like test* or test* ot *test* in if condition (5 Replies)
Discussion started by: johnjerome
5 Replies
LEARN ABOUT FREEBSD
atf-test-program
ATF-TEST-PROGRAM(1) BSD General Commands Manual ATF-TEST-PROGRAM(1)NAME
atf-test-program -- common interface to ATF test programs
SYNOPSIS
atf-test-program [-r resfile] [-s srcdir] [-v var1=value1 [.. -v varN=valueN]] test_case
atf-test-program -l
DESCRIPTION
Test programs written using the ATF libraries all share a common user interface, which is what this manual page describes. NOTE: There is no
binary known as atf-test-program; what is described in this manual page is the command-line interface exposed by the atf-c, atf-c++ and
atf-sh bindings.
In the first synopsis form, the test program will execute the provided test case and print its results to the standard output, unless other-
wise stated by the -r flag. Optionally, the test case name can be suffixed by ':cleanup', in which case the cleanup routine of the test case
will be executed instead of the test case body; see atf-test-case(4). Note that the test case is executed without isolation, so it can and
probably will create and modify files in the current directory. To execute test cases in a controller manner, you need a runtime engine that
understands the ATF interface. The recommended runtime engine is kyua(1). You should only execute test cases by hand for debugging pur-
poses.
In the second synopsis form, the test program will list all available test cases alongside their meta-data properties in a format that is
machine parseable. This list is processed by kyua(1) to know how to execute the test cases of a given test program.
The following options are available:
-l Lists available test cases alongside a brief description for each of them.
-r resfile Specifies the file that will receive the test case result. If not specified, the test case prints its results to stdout. If
the result of a test case needs to be parsed by another program, you must use this option to redirect the result to a file
and then read the resulting file from the other program. Note: do not try to process the stdout of the test case because
your program may break in the future.
-s srcdir The path to the directory where the test program is located. This is needed in all cases, except when the test program is
being executed from the current directory. The test program will use this path to locate any helper data files or utilities.
-v var=value Sets the configuration variable var to the value value.
SEE ALSO kyua(1)BSD March 2, 2014 BSD
07-24-2013
