shlock(1) [suse man page]
SHLOCK(1) InterNetNews Documentation SHLOCK(1) NAME
shlock - Create lock files for use in shell scripts SYNOPSIS
shlock [-b|-c|-u] -f name -p pid DESCRIPTION
shlock tries to create a lock file named name and write the process ID pid into it. If the file already exists, shlock will read the process ID from the file and test to see whether the process is currently running. If the process exists, then the file will not be created. shlock exits with a zero status if it could create the lock file, or non-zero if the file refers to a currently active process. OPTIONS
-b Process IDs are normally read and written in ASCII. If the -b flag is used, then they will be written as a binary int. -c If the -c flag is used, then shlock will not create a lock file, but will instead use the file to see if the lock is held by another program. If the lock is valid, the program will exit with a non-zero status; if the lock is not valid (i.e. invoking shlock without the flag would have succeeded), then the program will exit with a zero status. -f name name is the name of the lock file shlock attempts to create. If the file already exists, it will read the process ID from the file and exit with a non-zero status if this process is currently active. -p pid pid is the process ID to write into the file name. -u For compatibility with other systems, the -u flag is accepted as a synonym for -b since binary locks are used by many UUCP packages. EXAMPLES
The following example shows how shlock would be used within a shell script: LOCK=<pathrun in inn.conf>/LOCK.send trap 'rm -f ${LOCK} ; exit 1' 1 2 3 15 if shlock -p $$ -f ${LOCK} ; then # Do appropriate work. else echo "Locked by `cat ${LOCK}`" fi HISTORY
Written by Rich $alz <rsalz@uunet.uu.net> for InterNetNews after a description of HDB UUCP locking given by Peter Honeyman, and improved by Berend Reitsma to solve a race condition. Converted to POD by Julien Elie. $Id: shlock.pod 8357 2009-02-27 17:56:00Z iulius $ INN 2.5.2 2009-05-21 SHLOCK(1)
Check Out this Related Man Page
SCANLOGS(8) InterNetNews Documentation SCANLOGS(8) NAME
scanlogs - Summarize and rotate INN log files SYNOPSIS
scanlogs [norotate] DESCRIPTION
scanlogs summarizes the information recorded in the INN log files which reside in the pathlog directory set in inn.conf (see newslog(5) for further details about these log files). It is normally invoked by the news.daily(8) script which performs daily server maintenance tasks. It invokes "ctlinnd flushlogs" to close the news and error log files, rename them to add ".old" to the file names and open fresh news and error logs; the active file is also flushed to disk, along with the history database. By default, scanlogs rotates and cleans out the logs. It keeps up to logcycles old compressed log files in pathlog/OLD (the logcycles parameter can be set in inn.conf). scanlogs also keeps archives of the active file in this directory. It invokes tally.control if newgroup.log or rmgroup.log exists in pathlog (see the control.log entry of newslog(5) for more information about that). scanlogs displays the contents of errlog and news.crit, if non-empty, and runs innreport to summarize the contents of news and news.notice, and to update the unwanted.log file amongst other things (see more information about that in innreport(8)). OPTIONS
Only one option is currently accepted: norotate Using this option disables the rotating and cleaning aspect of the log processing: the logs files are only scanned for information and no contents are altered. If scanlogs is invoked more than once a day, the norotate option should be used to prevent premature log cleaning. FILES
See newslog(5) for the list of log files processed by scanlogs. HISTORY
Written by Landon Curt Noll <chongo@toad.com> and Rich $alz <rsalz@uunet.uu.net> for InterNetNews. Converted to POD by Julien Elie. $Id: scanlogs.pod 8357 2009-02-27 17:56:00Z iulius $ SEE ALSO
inn.conf(5), innreport(8), news.daily(8), newslog(5), shlock(1), tally.control(8). INN 2.5.2 2009-05-21 SCANLOGS(8)