04-30-2008
if test -f $file_exists
Hi,
I have a wiered problem probably unique to me.
if test -f "${LOGDIRE}/Component_Name.sql"
then
echo "<br>Synchronization success<br>"
else
echo "<br>Sorry! Synchronizing failed"
fi
Considering, the file is present always, the above condition returns different outputs in each execution. It is driving me nuts.
My suspision goes in this priority but I don't have reasons:
1) Syntax error in my code (KSH)
2) Influence of syntax error in other parts of the script (It is wiered that the above piece is before anything else in the script, it exits in case of error)
3) Load balanced cluster servers with two nodes. The $LOGDIRE is a space shared among several shared applications. It is a shared web hosting server
4) Influence of webserver environment - I use C executable, sqlplus, perl5, CGI and HPUX shell scripting and all are at different parts in the same shell script
5) I tried changing the save location, but doesn't seem to help
6 More Discussions You Might Find Interesting
1. Solaris
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)
Discussion started by: vikashtulsiyan
14 Replies
2. Shell Programming and Scripting
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)
Discussion started by: Max89
1 Replies
3. Shell Programming and Scripting
How to check weather a string is like test* or test* ot *test* in if condition (5 Replies)
Discussion started by: johnjerome
5 Replies
4. Shell Programming and Scripting
Hi,
I have a Python unit test cases source code file which contains more than a hundred test case methods. In that, some of the test case methods already have prefix 'test' where as some of them do not have. Now, I need to add the string 'test' (case-sensitive) as a prefix to those of the... (5 Replies)
Discussion started by: royalibrahim
5 Replies
5. Shell Programming and Scripting
I am testing shc to see if it would help with my need.
Im at a point where Im trying to compile and test the "test.ksh" file that comes in the tar ball :
shc-3.8.9> shc -v -r -f test.ksh
shc shll=ksh
shc =-c
shc =exec '%s' "$@"
shc =
shc opts=
shc: cc test.ksh.x.c -o test.ksh.x... (7 Replies)
Discussion started by: popeye
7 Replies
6. Shell Programming and Scripting
Often a wildcard test on files is needed.
Because test -f ... or have problems with zero or many arguments, and even ] has problems, and I have seen some ugly work-arounds,
I suggest the following simple function, to be defined somewhere at the beginning of the script:
file_exists() {
for... (4 Replies)
Discussion started by: MadeInGermany
4 Replies
SCRIPT(1) BSD General Commands Manual SCRIPT(1)
NAME
script -- make typescript of terminal session
SYNOPSIS
script [-akq] [-t time] [file [command ...]]
DESCRIPTION
The script utility makes a typescript of everything printed on your terminal. It is useful for students who need a hardcopy record of an
interactive session as proof of an assignment, as the typescript file can be printed out later with lpr(1).
If the argument file is given, script saves all dialogue in file. If no file name is given, the typescript is saved in the file typescript.
If the argument command is given, script will run the specified command with an optional argument vector instead of an interactive shell.
The following options are available:
-a Append the output to file or typescript, retaining the prior contents.
-k Log keys sent to program as well as output.
-q Run in quiet mode, omit the start and stop status messages.
-t time
Specify time interval between flushing script output file. A value of 0 causes script to flush for every character I/O event. The
default interval is 30 seconds.
The script ends when the forked shell (or command) exits (a control-D to exit the Bourne shell (sh(1)), and exit, logout or control-D (if
ignoreeof is not set) for the C-shell, csh(1)).
Certain interactive commands, such as vi(1), create garbage in the typescript file. The script utility works best with commands that do not
manipulate the screen. The results are meant to emulate a hardcopy terminal, not an addressable one.
ENVIRONMENT
The following environment variable is utilized by script:
SHELL If the variable SHELL exists, the shell forked by script will be that shell. If SHELL is not set, the Bourne shell is assumed. (Most
shells set this variable automatically).
SEE ALSO
csh(1) (for the history mechanism).
HISTORY
The script command appeared in 3.0BSD.
BUGS
The script utility places everything in the log file, including linefeeds and backspaces. This is not what the naive user expects.
It is not possible to specify a command without also naming the script file because of argument parsing compatibility issues.
When running in -k mode, echo cancelling is far from ideal. The slave terminal mode is checked for ECHO mode to check when to avoid manual
echo logging. This does not work when in a raw mode where the program being run is doing manual echo.
BSD
January 22, 2004 BSD