07-07-2011
have the script issue a "lock file"...either touch or write to a file that it alone knows about (ie, formatted file name), and then the script would check for this file upon launch. If the lock file is present, then someone else is running...or was, if not set it, process and then remove it. Secondary scripts can use a while [ -f $touch_file ] ;then sleep x; fi...and then run once it clears out.
Be sure that your Admins can identify the lock file externally in case it might fail mid-process, and would need to be deleted. Also, it might not hurt to use a file name format that allows for a random or session-based component so that each script launch would have its own lock file to manage, but one that could still be seen by other runs of the script.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I am using /usr/bin/ksh in AIX
I am reading the values of $dbname, $dbatmpdir/dbdir.$$, and $scope from a different file
All I have to do is check if $dbname exists in file $dbatmpdir/dbdir.$$ and
$scope should have a value either 'TABLE' or 'SCHEMA'.
When I execute the following code. I am... (3 Replies)
Discussion started by: tenderfoot
3 Replies
2. Shell Programming and Scripting
Hi,
How can we apply lock on a text file through Unix Ksh script. I did found a command flock (file descriptor) but am not very acquainted with the usage.
Can anybody tell me if I need to use Flock command for applying locks to a file while writing on it. If the person can explain the usage... (3 Replies)
Discussion started by: kum5256
3 Replies
3. Shell Programming and Scripting
Hi there,
pleas I want this script urgently. how to lock a directory by shell script? (12 Replies)
Discussion started by: joneggk
12 Replies
4. Shell Programming and Scripting
Can someone tell me when the script is called, what does it do? I can't see it is going to run anything. (1 Reply)
Discussion started by: dp100022
1 Replies
5. Shell Programming and Scripting
I am newbie in UNIX, so please excuse me for the stupid question.:)
Here is a problem:
I created ksh script where the part of the functionality include an opening of a second session with another shell process "runrep"(runrep is a custom reporting shell designed by Advent Geneva).
When I run my... (3 Replies)
Discussion started by: alexstar
3 Replies
6. Shell Programming and Scripting
Anyone know how to check a filename that contains a date and compare whiich file is older using a ksh shell script? The filename looks like aaaaa_20110615 (1 Reply)
Discussion started by: Bperl1967
1 Replies
7. Shell Programming and Scripting
From a shell script I'm trying to remove the first two files of whats returned from the head -2 command so I tried piping it to xargs rm -f but I can't get it to work.
How do I remove the files from the head command?
ls -al *clit* *servr* |sort -t_ -nk2 | head -2 |xargs rm -f (3 Replies)
Discussion started by: Bperl1967
3 Replies
8. Shell Programming and Scripting
Hi,
While running below code i am getting error as below
0403-004 Specify a parameter with this command.
Please look it below code and let me know about if condition.
Code is As below
#!/usr/bin/ksh
Infa_Src_Dir=$DIR/SrcFiles/pp
Load_Info_Lst_Path=$DIR/SrcFiles/pp... (1 Reply)
Discussion started by: samadhanpatil
1 Replies
9. Shell Programming and Scripting
My goal is to create a script that will check if in a test or production environment. I wrote this script to check $host variable to check which server I'm on but this script does not work.
if
then
BASE=/home/fmtest; export BASE
else
BASE=/home/fmprod; export BASE
fi
... (5 Replies)
Discussion started by: Bperl1967
5 Replies
10. Ubuntu
I wrote two shell scripts in UNIX that renames the same file and scheduled them at the same time.
The following are the steps that I followed:-
1. I wrote 2 scripts named s1.sh and s2.sh, both trying to add “exec_” prefix to the name of the files present in a folder i which already don't start... (4 Replies)
Discussion started by: piuli
4 Replies
exit(1) User Commands exit(1)
NAME
exit, return, goto - shell built-in functions to enable the execution of the shell to advance beyond its sequence of steps
SYNOPSIS
sh
exit [n]
return [n]
csh
exit [ ( expr )]
goto label
ksh
*exit [n]
*return [n]
DESCRIPTION
sh
exit will cause the calling shell or shell script to exit with the exit status specified by n. If n is omitted the exit status is that of
the last command executed (an EOF will also cause the shell to exit.)
return causes a function to exit with the return value specified by n. If n is omitted, the return status is that of the last command exe-
cuted.
csh
exit will cause the calling shell or shell script to exit, either with the value of the status variable or with the value specified by the
expression expr.
The goto built-in uses a specified label as a search string amongst commands. The shell rewinds its input as much as possible and searches
for a line of the form label: possibly preceded by space or tab characters. Execution continues after the indicated line. It is an error to
jump to a label that occurs between a while or for built-in command and its corresponding end.
ksh
exit will cause the calling shell or shell script to exit with the exit status specified by n. The value will be the least significant 8
bits of the specified status. If n is omitted then the exit status is that of the last command executed. When exit occurs when executing
a trap, the last command refers to the command that executed before the trap was invoked. An end-of-file will also cause the shell to exit
except for a shell which has the ignoreeof option (See set below) turned on.
return causes a shell function or '.' script to return to the invoking script with the return status specified by n. The value will be the
least significant 8 bits of the specified status. If n is omitted then the return status is that of the last command executed. If return
is invoked while not in a function or a '.' script, then it is the same as an exit.
On this man page, ksh(1) commands that are preceded by one or two * (asterisks) are treated specially in the following ways:
1. Variable assignment lists preceding the command remain in effect when the command completes.
2. I/O redirections are processed after variable assignments.
3. Errors cause a script that contains them to abort.
4. Words, following a command preceded by ** that are in the format of a variable assignment, are expanded with the same rules as a vari-
able assignment. This means that tilde substitution is performed after the = sign and word splitting and file name generation are not
performed.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
break(1), csh(1), ksh(1), sh(1), attributes(5)
SunOS 5.10 15 Apr 1994 exit(1)