Sponsored Content
Full Discussion: What does this mean?
Top Forums Shell Programming and Scripting What does this mean? Post 302602782 by gary_w on Tuesday 28th of February 2012 10:33:38 AM
Old 02-28-2012
Just a tip, become familiar with the "man" command, which shows you the manual page for a command i.e :
Code:
$ man date

to learn about the date command and its options. Of course these days you can ask the google too. When I was learning I did what you are doing, taking an existing script and studying it line by line, doing a man and reading about each command I was not familiar with. When you learn what it does, add a comment above or to the right of it, like what agama did for you. Keep a copy of your edited script in your own directory for reference. Pretty soon it will start clicking. Then you need to learn the vi editor!

Perusing posts here will be a help too, use the search functionality for a specific question. Believe me, whatever question you have, you will not be the first to ask it. Use a meaningful subject line for your post, you'll get more views and replies, plus future searchers will have a better chance at finding information.

People here are real helpful, but mention the system and shell you are using too when asking a question, it matters. Be thankful there is a resource like this site. Back in the day when I asked a question, the response was usually a gruff "RTFM!"! lol

Last edited by gary_w; 02-28-2012 at 11:38 AM..
 
FLOCK(1)							   User Commands							  FLOCK(1)

NAME
flock - manage locks from shell scripts SYNOPSIS
flock [-sxon] [-w timeout] lockfile [-c] command... flock [-sxon] [-w timeout] lockdir [-c] command... flock [-sxun] [-w timeout] fd DESCRIPTION
This utility manages flock(2) locks from within shell scripts or the command line. The first and second forms wraps the lock around the executing a command, in a manner similar to su(1) or newgrp(1). It locks a specified file or directory, which is created (assuming appropriate permissions), if it does not already exist. The third form is convenient inside shell scripts, and is usually used the following manner: ( flock -n 9 || exit 1 # ... commands executed under lock ... ) 9>/var/lock/mylockfile The mode used to open the file doesn't matter to flock; using > or >> allows the lockfile to be created if it does not already exist, how- ever, write permission is required; using < requires that the file already exists but only read permission is required. By default, if the lock cannot be immediately acquired, flock waits until the lock is available. OPTIONS
-s, --shared Obtain a shared lock, sometimes called a read lock. -x, -e, --exclusive Obtain an exclusive lock, sometimes called a write lock. This is the default. -u, --unlock Drop a lock. This is usually not required, since a lock is automatically dropped when the file is closed. However, it may be required in special cases, for example if the enclosed command group may have forked a background process which should not be hold- ing the lock. -n, --nb, --nonblock Fail (with an exit code of 1) rather than wait if the lock cannot be immediately acquired. -w, --wait, --timeout seconds Fail (with an exit code of 1) if the lock cannot be acquired within seconds seconds. Decimal fractional values are allowed. -o, --close Close the file descriptor on which the lock is held before executing command. This is useful if command spawns a child process which should not be holding the lock. -c, --command command Pass a single command to the shell with -c. -h, --help Print a help message. AUTHOR
Written by H. Peter Anvin <hpa@zytor.com>. COPYRIGHT
Copyright (C) 2003-2006 H. Peter Anvin. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU- LAR PURPOSE. SEE ALSO
flock(2) AVAILABILITY
The flock command is part of the util-linux package and is available from ftp://ftp.kernel.org/pub/linux/utils/util-linux/. util-linux February 2006 FLOCK(1)
All times are GMT -4. The time now is 07:01 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy