10 More Discussions You Might Find Interesting
1. IP Networking
Ggod evening.
I need your help please, in a Production system there is a process that download a xls file from an URL which is IMF(International Monetary Fund) and afterwards to be loaded into a databse table.
When testing conectivity from a unix server to IMF seems to work but when editing it... (9 Replies)
Discussion started by: alexcol
9 Replies
2. Shell Programming and Scripting
Hello ALL ,
i am requesting help on for this script i am preparing to get the result of a query in a excel sheet :
current Error:
Script : NO Excel file created.
requesting to know where i am going wrong.
#!/bin/ksh... (2 Replies)
Discussion started by: anirudhkashikar
2 Replies
3. Forum Support Area for Unregistered Users & Account Problems
User name: Michael Mullig
<removed email addresses> (1 Reply)
Discussion started by: Mike Mullig
1 Replies
4. Shell Programming and Scripting
Hi
I have a problem to resolve, I think sed is the best option, and I am not successful yet.
Have a UNIX file which has records as of the 2 character state codes like
NY
NJ
PA
DE
From the file I need to create this as a variable in the same script or another file -... (7 Replies)
Discussion started by: snair2010
7 Replies
5. Shell Programming and Scripting
Hi,
I'm very new to bash scripting and Linux in general. I'm running Ubuntu Server 10.04 and trying to write a bash script to launch a program. In doing so, I've come across a couple of things that I obviously don't understand. Here is a short script that exemplifies those things:
... (9 Replies)
Discussion started by: Carson Dyle
9 Replies
6. Shell Programming and Scripting
Hello Folks,
I would very much appreciate if I could get help/suggestions on a particular sed usage. I have to write a script to take version info from a version file, compute the image name, print error if the image does not exist.
The version file looks like below:
"
#
# version.cfg
#... (3 Replies)
Discussion started by: fatimap
3 Replies
7. UNIX for Advanced & Expert Users
I gotta write a command to change the accounts in /etc/passwd that use a shell other than the bash to bash shell. those accounts that dont use a shell shouldnt get modified. assuming all the shell programs end in sh and other programs dont. and the result should go into /etc/passwd.rev
any hint? (4 Replies)
Discussion started by: metalwarrior
4 Replies
8. Shell Programming and Scripting
Fairly new scripter so please bare with me if what I have done below is not according to standards.
Okay...heres what I am trying to do. I have a pattern that I need to search for in a directory. This gives me a list of files that includes a control file that contains totals of the line nos for... (3 Replies)
Discussion started by: alfredo123
3 Replies
9. AIX
Hello there!
I have a RS-6000 7043-140 machine with AIX version 4.1.5, that is
working for almost 8 years now. It has a tty monitor. My problem
started when I upgraded my machine to install a gxt250 graphics adapter
card together with a 15" AOC VGA Monitor, logitech keyboard and mouse, ... (2 Replies)
Discussion started by: bright_genius
2 Replies
10. Solaris
Ladies/Gentlemen,
I am looking for a web-based tool to keep track of my Sun inventory. The following list of fields are fields I would like to store: Root Passwd (needs to be secure) / Hostid / Console Port / IP Address / Platform / Application / Hostname . . . you get the point.
Do any of... (4 Replies)
Discussion started by: pc9456
4 Replies
LOCKFILE(1) General Commands Manual LOCKFILE(1)
NAME
lockfile - conditional semaphore-file creator
SYNOPSIS
lockfile -sleeptime | -r retries |
-l locktimeout | -s suspend | -! | -ml | -mu | filename ...
DESCRIPTION
lockfile can be used to create one or more semaphore files. If lockfile can't create all the specified files (in the specified order), it
waits sleeptime (defaults to 8) seconds and retries the last file that didn't succeed. You can specify the number of retries to do until
failure is returned. If the number of retries is -1 (default, i.e., -r-1) lockfile will retry forever.
If the number of retries expires before all files have been created, lockfile returns failure and removes all the files it created up till
that point.
Using lockfile as the condition of a loop in a shell script can be done easily by using the -! flag to invert the exit status. To prevent
infinite loops, failures for any reason other than the lockfile already existing are not inverted to success but rather are still returned
as failures.
All flags can be specified anywhere on the command line, they will be processed when encountered. The command line is simply parsed from
left to right.
All files created by lockfile will be read-only, and therefore will have to be removed with rm -f.
If you specify a locktimeout then a lockfile will be removed by force after locktimeout seconds have passed since the lockfile was last
modified/created (most likely by some other program that unexpectedly died a long time ago, and hence could not clean up any leftover lock-
files). Lockfile is clock skew immune. After a lockfile has been removed by force, a suspension of suspend seconds (defaults to 16) is
taken into account, in order to prevent the inadvertent immediate removal of any newly created lockfile by another program (compare SUSPEND
in procmail(1)).
Mailbox locks
If the permissions on the system mail spool directory allow it, or if lockfile is suitably setgid, it will be able to lock and unlock your
system mailbox by using the options -ml and -mu respectively.
EXAMPLES
Suppose you want to make sure that access to the file "important" is serialised, i.e., no more than one program or shell script should be
allowed to access it. For simplicity's sake, let's suppose that it is a shell script. In this case you could solve it like this:
...
lockfile important.lock
...
access_"important"_to_your_hearts_content
...
rm -f important.lock
...
Now if all the scripts that access "important" follow this guideline, you will be assured that at most one script will be executing between
the `lockfile' and the `rm' commands.
ENVIRONMENT
LOGNAME used as a hint to determine the invoker's loginname
FILES
/etc/passwd to verify and/or correct the invoker's loginname (and to find out his HOME directory, if needed)
/var/mail/$LOGNAME.lock
lockfile for the system mailbox, the environment variables present in here will not be taken from the environment,
but will be determined by looking in /etc/passwd
SEE ALSO
rm(1), mail(1), sendmail(8), procmail(1)
DIAGNOSTICS
Filename too long, ... Use shorter filenames.
Forced unlock denied on "x"
No write permission in the directory where lockfile "x" resides, or more than one lockfile trying to force a lock at
exactly the same time.
Forcing lock on "x" Lockfile "x" is going to be removed by force because of a timeout (compare LOCKTIMEOUT in procmail(1)).
Out of memory, ... The system is out of swap space.
Signal received, ... Lockfile will remove anything it created till now and terminate.
Sorry, ... The retries limit has been reached.
Truncating "x" and retrying lock
"x" does not seem to be a valid filename.
Try praying, ... Missing subdirectories or insufficient privileges.
BUGS
Definitely less than one.
WARNINGS
The behavior of the -! flag, while useful, is not necessarily intuitive or consistent. When testing lockfile's return value, shell script
writers should consider carefully whether they want to use the -! flag, simply reverse the test, or do a switch on the exact exitcode. In
general, the -! flag should only be used when lockfile is the conditional of a loop.
MISCELLANEOUS
Lockfile is NFS-resistant and eight-bit clean.
NOTES
Calling up lockfile with the -h or -? options will cause it to display a command-line help page. Calling it up with the -v option will
cause it to display its version information.
Multiple -! flags will toggle the return status.
Since flags can occur anywhere on the command line, any filename starting with a '-' has to be preceded by './'.
The number of retries will not be reset when any following file is being created (i.e., they are simply used up). It can, however, be re-
set by specifying -rnewretries after every file on the command line.
Although files with any name can be used as lockfiles, it is common practice to use the extension `.lock' to lock mailfolders (it is ap-
pended to the mailfolder name). In case one does not want to have to worry about too long filenames and does not have to conform to any
other lockfilename convention, then an excellent way to generate a lockfilename corresponding to some already existing file is by taking
the prefix `lock.' and appending the i-node number of the file which is to be locked.
SOURCE
This program is part of the procmail mail-processing-package (v3.22) available at http://www.procmail.org/ or ftp.procmail.org in pub/proc-
mail/.
MAILINGLIST
There exists a mailinglist for questions relating to any program in the procmail package:
<procmail-users@procmail.org>
for submitting questions/answers.
<procmail-users-request@procmail.org>
for subscription requests.
If you would like to stay informed about new versions and official patches send a subscription request to
procmail-announce-request@procmail.org
(this is a readonly list).
AUTHORS
Stephen R. van den Berg
<srb@cuci.nl>
Philip A. Guenther
<guenther@sendmail.com>
BuGless 2001/06/23 LOCKFILE(1)