![]() |
|
|
|||||||
| Home | Forums | Register | Rules & FAQ | Members List | Arcade | Search | Today's Posts | Mark Forums Read |
| UNIX for Advanced & Expert Users Advanced UNIX and Linux questions go here. Expert-to-Expert. |
Other UNIX.COM Threads You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| TAHI Test Suite 3.0.13 (IPv6 Conformance Test Tool branch) | iBot | Software Releases - RSS News | 0 | 04-06-2008 09:20 AM |
| test and .test in same directory | vikashtulsiyan | SUN Solaris | 14 | 12-27-2007 10:25 PM |
| Keithley Introduces Linux-Based RF Parametric Test Systems - Test and Measurement.com | iBot | UNIX and Linux RSS News | 0 | 07-23-2007 07:30 AM |
| test $# | hamsasal | UNIX for Dummies Questions & Answers | 2 | 10-04-2005 04:43 AM |
| BDF test for > 90% | svp4444 | UNIX for Dummies Questions & Answers | 6 | 09-05-2001 08:49 AM |
![]() |
|
|
Submit Tools | LinkBack | Thread Tools | Search this Thread | Display Modes |
|
|||
|
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 |
| Forum Sponsor | ||
|
|
|
|||
|
Sounds very much like the load balancing would be the explanation, although what exactly causes the $LOGDIRE to occasionally not be mounted / available / whatever is completely open, without more information about what you are using. NFS? The OS is apparently HPukes.
|
|||
| Google UNIX.COM |