Группа :: Работа с файлами
Пакет: lockfile-progs
навигация по пакетам
Главная Изменения Спек Патчи Исходники Загрузить Gear Bugs and FR Repocop
pax_global_header 0000666 0000000 0000000 00000000064 12132611403 0014503 g ustar 00root root 0000000 0000000 52 comment=40ea85e5d0d6f22ebcf250248c98c11bf8f58a7a
lockfile-progs-0.1.11/ 0000755 0000000 0000000 00000000000 12132611403 0014501 5 ustar 00root root 0000000 0000000 lockfile-progs-0.1.11/.gear/ 0000755 0000000 0000000 00000000000 12132611403 0015475 5 ustar 00root root 0000000 0000000 lockfile-progs-0.1.11/.gear/rules 0000644 0000000 0000000 00000000007 12132611403 0016547 0 ustar 00root root 0000000 0000000 tar: .
lockfile-progs-0.1.11/.gitignore 0000644 0000000 0000000 00000000171 12132611403 0016470 0 ustar 00root root 0000000 0000000 *~
\#*
.\#*
/bin
/debian/files
/debian/stamp-build
/debian/substvars
/debian/tmp
/lockfile-create
/lockfile-progs.o
/man
lockfile-progs-0.1.11/COPYING 0000644 0000000 0000000 00000043127 12132611403 0015543 0 ustar 00root root 0000000 0000000 GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.) You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their
rights.
We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.
Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and
modification follow.
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language. (Hereinafter, translation is included without limitation in
the term "modification".) Each licensee is addressed as "you".
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.
You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.
b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.
c) If the modified program normally reads commands interactively
when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.
In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such
an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable. However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.
If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.
5. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.
7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all. For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.
9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.
10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Also add information on how to contact you by electronic and paper mail.
If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) 19yy name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision' (which makes passes at compilers) written by James Hacker.
<signature of Ty Coon>, 1 April 1989
Ty Coon, President of Vice
This General Public License does not permit incorporating your program into
proprietary programs. If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library. If this is what you want to do, use the GNU Library General
Public License instead of this License.
lockfile-progs-0.1.11/Makefile 0000644 0000000 0000000 00000001725 12132611403 0016146 0 ustar 00root root 0000000 0000000
LOADLIBES := -llockfile
CFLAGS := -g -Wall -Werror -O2
all: lockfile-create
rm -rf bin
mkdir -p bin
cp -a lockfile-create bin
cp -a lockfile-create bin/mail-lock
cd bin && ln lockfile-create lockfile-remove
cd bin && ln lockfile-create lockfile-touch
cd bin && ln mail-lock mail-unlock
cd bin && ln mail-lock mail-touchlock
mkdir -p man
cp -a lockfile-progs.1 man
(cd man && ln -sf lockfile-progs.1 lockfile-create.1 && \
ln -sf lockfile-progs.1 lockfile-remove.1 && \
ln -sf lockfile-progs.1 lockfile-touch.1 && \
ln -sf lockfile-progs.1 mail-lock.1 && \
ln -sf lockfile-progs.1 mail-unlock.1 && \
ln -sf lockfile-progs.1 mail-touchlock.1)
.PHONY: all
lockfile-create: lockfile-progs.o
${CC} -o $@ ${LDFLAGS} $^ ${LOADLIBES}
distclean: clean
clean:
rm -f lockfile-create lockfile-remove lockfile-touch
rm -f mail-lock mail-unlock mail-touchlock
rm -f *.o *~
rm -rf bin man
.PHONY: clean distclean
lockfile-progs-0.1.11/TODO 0000644 0000000 0000000 00000000074 12132611403 0015172 0 ustar 00root root 0000000 0000000 -*-text-*-
* Need to add support for the new L_PID option.
lockfile-progs-0.1.11/debian/ 0000755 0000000 0000000 00000000000 12132611403 0015723 5 ustar 00root root 0000000 0000000 lockfile-progs-0.1.11/debian/changelog 0000644 0000000 0000000 00000005426 12132611403 0017604 0 ustar 00root root 0000000 0000000 lockfile-progs (0.1.11) unstable; urgency=low
* Add --quiet and --verbose options. (closes: #272539)
* Use hard links for duplicate binaries. (closes: #382730)
* Respect DEB_BUILD_OPTIONS nostrip. (closes: #437491)
* Fix manpage to reflect changes to liblockfile --retry.
(closes: #161685, #244314, #360474)
* Add support for --lock-name (-l). (closes: #416355)
-- Rob Browning <rlb@defaultvalue.org> Fri, 24 Aug 2007 17:35:23 -0700
lockfile-progs (0.1.10) unstable; urgency=low
* update manpage to fix dashes under utf-8. (closes: #159907)
* recompile to fix prelink problem. (closes: #231550)
* fix manpage to note --try like semantics of --retry.
-- Rob Browning <rlb@defaultvalue.org> Sat, 28 Feb 2004 11:44:30 -0600
lockfile-progs (0.1.9) unstable; urgency=low
* Add command tool names to manpages. (closes: #88510)
* Update my email address.
-- Rob Browning <rlb@defaultvalue.org> Tue, 17 Jul 2001 12:38:34 -0500
lockfile-progs (0.1.8) unstable; urgency=low
* Add Build-Depends: liblockfile-dev (Closes: Bug#94948, Bug#84547).
* Move manpages to /usr/share/man (Closes: Bug#80755, Bug#91205).
* Move docs to /usr/share (Closes: Bug#91571).
-- Rob Browning <rlb@cs.utexas.edu> Mon, 23 Apr 2001 15:24:26 -0500
lockfile-progs (0.1.7) unstable; urgency=low
* Update to depend on liblockfile1 (Closes: Bug#44819)
* Support new lockfile_create() signature.
-- Rob Browning <rlb@cs.utexas.edu> Fri, 24 Sep 1999 18:41:58 -0500
lockfile-progs (0.1.6) unstable; urgency=low
* Really fix return codes (Closes: Bug#34279)
-- Rob Browning <rlb@cs.utexas.edu> Sat, 29 May 1999 13:36:42 -0500
lockfile-progs (0.1.5) unstable; urgency=low
* Programs now return more meaningful result codes (Closes: Bug#31254).
-- Rob Browning <rlb@cs.utexas.edu> Sun, 17 Jan 1999 20:39:29 -0600
lockfile-progs (0.1.4) unstable; urgency=low
* Don't allow locking arbitrary mailbox (Closes: Bug#28773).
* Clean up code to use getopt.
* Add --oneshot option to lock touching programs.
* Add --retry-count option to locking programs.
-- Rob Browning <rlb@cs.utexas.edu> Sat, 21 Nov 1998 01:06:27 -0600
lockfile-progs (0.1.3) unstable; urgency=low
* Rebuild as root. Libtricks built a broken .deb (a file that should
have been a symlink was a truncated file of garbage).
-- Rob Browning <rlb@cs.utexas.edu> Fri, 30 Oct 1998 16:11:34 -0600
lockfile-progs (0.1.2) unstable; urgency=low
* Make mail lock programs a separate binary, and make them sgid mail.
-- Rob Browning <rlb@cs.utexas.edu> Fri, 30 Oct 1998 15:47:17 -0600
lockfile-progs (0.1.1) unstable; urgency=low
* Initial release.
* This is beta code, so be a little cautious. I don't think there are
any *serious* bugs, but...
-- Rob Browning <rlb@cs.utexas.edu> Mon, 19 Oct 1998 16:53:40 -0500
lockfile-progs-0.1.11/debian/control 0000644 0000000 0000000 00000001340 12132611403 0017324 0 ustar 00root root 0000000 0000000 Source: lockfile-progs
Section: misc
Priority: optional
Maintainer: Rob Browning <rlb@defaultvalue.org>
Build-Depends: liblockfile-dev
Standards-Version: 3.6.1
Package: lockfile-progs
Section: misc
Priority: optional
Architecture: any
Depends: ${shlibs:Depends}
Priority: optional
Description: Programs for locking and unlocking files and mailboxes
This package includes several programs to safely lock and unlock
files and mailboxes from the command line. These include:
.
lockfile-create
lockfile-remove
lockfile-touchlock
mail-lock
mail-unlock
mail-touchlock
.
These programs use liblockfile to perform the file locking and
unlocking, so they are guaranteed compatible with Debian's
file locking policies.
lockfile-progs-0.1.11/debian/copyright 0000644 0000000 0000000 00000000276 12132611403 0017663 0 ustar 00root root 0000000 0000000 This is a Debian specific package, so there is no upstream source.
lockfile-progs is covered under the terms of the GNU Public License.
See /usr/share/common-licenses/GPL for more details.
lockfile-progs-0.1.11/debian/prerm 0000755 0000000 0000000 00000000206 12132611403 0016774 0 ustar 00root root 0000000 0000000 #!/bin/sh
set -e
if [ \( "$1" = upgrade -o "$1" = remove \) -a -L /usr/doc/lockfile-progs ]
then
rm -f /usr/doc/lockfile-progs
fi
lockfile-progs-0.1.11/debian/rules 0000755 0000000 0000000 00000005040 12132611403 0017002 0 ustar 00root root 0000000 0000000 #!/usr/bin/make -f
# Copyright 1998 Rob Browning <rlb@defaultvalue.org>
# This file is covered under the terms of the Gnu Public License.
SHELL=/bin/bash
# the architecture of the package
arch := $(shell dpkg --print-architecture)
# The Debian target name of the package
target := ${arch}-debian-linux-gnu
export CFLAGS := -DDEBIAN -O2 -g
export LDFLAGS := -g
debian/stamp-build:
${checkdir}
make
touch debian/stamp-build
build: debian/stamp-build
clean:
${checkdir}
rm -f build debian/stamp-* debian/substvars
-make distclean
find -name '*~' | xargs --no-run-if-empty rm -f
-rm -rf debian/tmp debian/files*
binary-indep: checkroot build
${checkdir}
# There are no architecture-independent files to be uploaded
# generated by this package. If there were any they would be
# made here.
binary-arch: checkroot build
${checkdir}
rm -rf debian/tmp
install -d debian/tmp
# binaries
install -d debian/tmp/usr/bin
cp -a bin/* debian/tmp/usr/bin/
ifeq (,$(findstring nostrip,$(DEB_BUILD_OPTIONS)))
strip --strip-unneeded debian/tmp/usr/bin/*
endif
# manpages
install -d debian/tmp/usr/share/man/man1
cp -a man/* debian/tmp/usr/share/man/man1
find debian/tmp/usr/share/man -type f | xargs gzip -9v
(cd debian/tmp/usr/share/man && \
for file in `find -type l`; \
do \
ln -sf lockfile-progs.1.gz $${file}.gz; \
rm -f $${file}; \
done)
install -d debian/tmp/usr/share/doc/lockfile-progs
cp debian/changelog debian/tmp/usr/share/doc/lockfile-progs/
find debian/tmp/usr/share/doc/lockfile-progs -type f | xargs gzip -9v
cp debian/copyright debian/tmp/usr/share/doc/lockfile-progs
# Mangle permissions to conform.
chown -R root.root debian/tmp
find debian/tmp -type d | xargs chmod 755
find debian/tmp -not -type d -a -not -type l | xargs chmod 644
chmod 755 debian/tmp/usr/bin/*
chown :mail debian/tmp/usr/bin/mail-lock
chmod g+s debian/tmp/usr/bin/mail-lock
# control scripts
install -d debian/tmp/DEBIAN
cp debian/prerm debian/tmp/DEBIAN
chmod 755 debian/tmp/DEBIAN/prerm
# Now really get busy.
dpkg-shlibdeps `find debian/tmp/usr/bin/ -type f`
dpkg-gencontrol -isp -plockfile-progs
dpkg --build debian/tmp ..
define checkdir
test -f debian/rules
test -f lockfile-progs.c
endef
# Below here is fairly generic really
binary: binary-indep binary-arch
source diff:
@echo >&2 'source and diff are obsolete - use dpkg-source -b'; false
checkroot:
${checkdir}
test root = "`whoami`"
.PHONY: binary binary-arch binary-indep clean checkroot
lockfile-progs-0.1.11/lockfile-progs.1 0000644 0000000 0000000 00000007430 12132611403 0017507 0 ustar 00root root 0000000 0000000 '\" t
.\" ** The above line should force tbl to be a preprocessor **
.\" Man page for man
.\"
.\" Copyright (C), 1998-2007, Rob Browning <rlb@defaultvalue.org>
.\"
.\" You may distribute under the terms of the GNU General Public
.\" License as specified in the file COPYING that comes with the
.\" lockfile\-progs distribution.
.\"
.TH lockfile\-progs 1 "23 August 2007" "0.1.11" "Lockfile programs"
.SH NAME
lockfile\-progs \- command\-line programs to safely lock and unlock
files and mailboxes (via liblockfile).
.SH SYNOPSIS
\fBmail\-lock\fR [ \-\-retry \fIretry\-count\fR ]
.br
\fBmail\-unlock\fR
.br
\fBmail\-touchlock\fR [ \-\-oneshot ]
\fBlockfile\-create\fR [ \-\-retry \fIretry\-count\fR ] \fIfilename\fR
.br
\fBlockfile\-remove\fR \fIfilename\fR
.br
\fBlockfile\-touch\fR [ \-\-oneshot ] \fIfilename\fR
.SH DESCRIPTION
.B lockfile\-progs
provide a method to lock and unlock mailboxes and files safely (via
liblockfile).
By default, the \fIfilename\fR argument refers to the name of the file
to be locked, and the name of the lockfile will be
\fIfilename\fR .lock. However, if the \-\-lock-name argument is specified,
then \fIfilename\fR will be taken as the name of the lockfile itself.
\fBmail\-lock:\fR lock the current user's mailbox.
.br
\fBmail\-unlock:\fR unlock the current user's mailbox.
.br
\fBmail\-touchlock:\fR touch the lock on the current user's mailbox.
Each of the mail locking commands is applied to the file
/var/spool/mail/<user>, if possible, where <user> is the name of the
current user (determined from the effective uid via geteuid(2)).
\fBlockfile\-create:\fR lock a given file.
.br
\fBlockfile\-remove:\fR remove the lock on a given file.
.br
\fBlockfile\-touch:\fR touch the lock on a given file.
Once a file is locked, the lock must be touched at least once every
five minutes, or it will be considered stale and a subsequent attempt
to lock the file will succeed. For both of the locking commands
(\fBmail\-touchlock\fR and \fBlockfile\-touch\fR), the \-\-oneshot
argument causes the program to touch the lock and exit immediately.
Otherwise the program will loop forever, touching the lock once every
minute until it is killed.
For both of the locking commands (\fBmail\-lock\fR and
\fBlockfile\-create\fR), the \-\-retry argument specifies (as an
integer) the maximum number of times to retry locking the file before
giving up if attempts are failing. Each retry will be delayed a
little longer than the last (in 5 second increments) until a maximum
delay of one minute between retries is reached. The default retry
count is 9 which, if all 9 attempts to lock the file fail, will give
up after 180 seconds (3 minutes).
The \fBlockfile\-create\fR, \fBlockfile\-remove\fR, and
\fBlockfile-touch\fR commands will also accept these options:
.TP
\fB\-l\fR, \fB\-\-lock-name\fR
Use \fIfilename\fR as the explict lock file name instead of
appending .lock to \fIfilename\fR.
.PP
All of the following commands will accept these options:
.TP
\fB\-q\fR, \fB\-\-quiet\fR
Supress any output. Success or failure will only be indicated by the
exit status.
.TP
\fB\-v\fR, \fB\-\-verbose\fR
Enable diagnostic output.
.SH EXAMPLES
.B Locking a file during a lengthy process:
lockfile\-create /some/file
lockfile\-touch /some/file &
# Save the PID of the lockfile\-touch process
BADGER="$!"
do\-something\-important\-with /some/file
kill "${BADGER}"
lockfile\-remove /some/file
.SH "EXIT STATUS"
.TP
.B 0
Successful program execution.
.TP
\fBANYTHING ELSE\fR
Some problem was encountered.
.SH "SEE ALSO"
.BR maillock (3)
.br
.BR touchlock (3)
.br
.BR mailunlock (3)
.br
.BR lockfile\-create (1)
.br
.BR lockfile\-remove (1)
.br
.BR lockfile\-touch (1)
.br
.BR lockfile_create (3)
.br
.BR lockfile_remove (3)
.br
.BR lockfile_touch (3)
.br
.SH HISTORY
1998 \- Written by Rob Browning <rlb@defaultvalue.org>.
lockfile-progs-0.1.11/lockfile-progs.c 0000644 0000000 0000000 00000013716 12132611403 0017575 0 ustar 00root root 0000000 0000000 /* lockfile-progs.c
Copyright 1998 Rob Browning <rlb@defaultvalue.org>
This code is covered under the terms of the Gnu Public License.
See the accompanying COPYING file for details.
To do:
It might be useful at some point to support a --user option to
mail-lock that can only be used by the superuser (of course, they
could just use lockfile-create with an appropriate path...
*/
#define _GNU_SOURCE
#include <lockfile.h>
#include <unistd.h>
#include <stdlib.h>
#include <stdio.h>
#include <signal.h>
#include <stdarg.h>
#include <string.h>
#include <getopt.h>
#include <pwd.h>
#include <sys/types.h>
static const char *action = NULL;
static char *target_file = NULL;
static int retry_count = 9; /* This will be a maximum of 3 minutes */
static int touchlock_oneshot = 0;
/* not used yet, so not documented... */
static int lockfile_verbosity = 1;
static int lockfile_add_dot_lock_to_name = 1;
static int result = 0;
static int
msg(FILE *f, const char *fmt, ...) __attribute__ ((format (printf, 2, 3)));
static int
msg(FILE *f, const char *fmt, ...)
{
int rc = 0;
if(lockfile_verbosity > 0)
{
va_list args;
va_start(args, fmt);
rc = vfprintf(f, fmt, args);
va_end(args);
}
return rc;
}
static void
usage(const char *command_name, FILE *file) {
char *usage_str = NULL;
if(strcmp(command_name, "mail-lock") == 0) {
usage_str = "usage: mail-lock [--retry retry-count]\n";
} else if(strcmp(command_name, "mail-unlock") == 0) {
usage_str = "usage: mail-unlock\n";
} else if(strcmp(command_name, "mail-touchlock") == 0) {
usage_str = "usage: mail-touchlock [--oneshot]\n";
} else if(strcmp(command_name, "lockfile-create") == 0) {
usage_str =
"usage: lockfile-create [--retry retry-count] [--lock-name] file\n";
} else if(strcmp(command_name, "lockfile-remove") == 0) {
usage_str = "usage: lockfile-remove [--lock-name] file\n";
} else if(strcmp(command_name, "lockfile-touch") == 0) {
usage_str = "usage: lockfile-touch [--oneshot] [--lock-name] file\n";
} else {
msg(stderr, "lockfile: big problem - unknown command name: %s\n",
command_name);
exit(1);
}
msg(file, "%s", usage_str);
}
static void
parse_arguments(const int argc, char *argv[]) {
int opt_result;
const char *short_opts = "r:olqv";
struct option long_opts[] = {
{ "retry", required_argument, NULL, 'r' },
{ "oneshot", no_argument, NULL, 'o' },
{ "lock-name", no_argument, NULL, 'l' },
{ "quiet", no_argument, NULL, 'q' },
{ "verbose", no_argument, NULL, 'v' },
{ NULL, 0, NULL, 0 }
};
char *cmd_name = rindex(argv[0], '/');
int mail_cmd_p = 0;
if(cmd_name != NULL) {
/* Skip the '/' */
cmd_name++;
} else {
cmd_name = argv[0];
}
while((opt_result = getopt_long(argc, argv,
short_opts, long_opts, NULL)) != -1)
{
switch(opt_result)
{
case 'o':
touchlock_oneshot = 1;
break;
case 'q':
lockfile_verbosity = 0;
break;
case 'v':
lockfile_verbosity = 2;
break;
case 'l':
lockfile_add_dot_lock_to_name = 0;
break;
case 'r':
{
char *rest_of_string;
long tmp_value = strtol(optarg, &rest_of_string, 10);
if((tmp_value == 0) && (rest_of_string == optarg)) {
/* Bad value */
msg(stderr, "%s: bad retry-count value\n", cmd_name);
usage(cmd_name, stderr);
exit(1);
} else {
retry_count = tmp_value;
}
}
break;
default:
msg(stderr, "%s: getopt returned impossible value 0%o.\n",
cmd_name, opt_result);
exit(1);
break;
}
}
if(strcmp(cmd_name, "mail-lock") == 0) {
action = "lock";
mail_cmd_p = 1;
}
else if(strcmp(cmd_name, "mail-unlock") == 0) {
action = "unlock";
mail_cmd_p = 1;
}
else if(strcmp(cmd_name, "mail-touchlock") == 0) {
action = "touch";
mail_cmd_p = 1;
}
else if(strcmp(cmd_name, "lockfile-create") == 0) {
action = "lock";
}
else if(strcmp(cmd_name, "lockfile-remove") == 0) {
action = "unlock";
}
else if(strcmp(cmd_name, "lockfile-touch") == 0) {
action = "touch";
} else {
usage(cmd_name, stderr);
exit(1);
}
if(mail_cmd_p) {
if(optind == argc) {
uid_t user_id = geteuid();
struct passwd *user_info = getpwuid(user_id);
if(user_info == NULL) {
msg(stderr, "%s: fatal error, can't find info for user id %ud\n",
cmd_name, user_id);
exit(1);
}
if(asprintf(&target_file, "/var/spool/mail/%s",
user_info->pw_name) == -1) {
msg(stderr, "asprintf failed: line %d\n", __LINE__);
exit(1);
}
} else {
usage(cmd_name, stderr);
exit(1);
}
} else {
if((argc - optind) != 1) {
usage(cmd_name, stderr);
exit(1);
}
target_file = argv[optind];
}
}
static void
handle_touchdeath(int sig) {
exit(result);
}
int
main(int argc, char *argv[]) {
const char *lock_name_pattern = "%s";
char *lockfilename = NULL;
parse_arguments(argc, argv);
if(lockfile_add_dot_lock_to_name)
lock_name_pattern = "%s.lock";
if(asprintf(&lockfilename, lock_name_pattern, target_file) == -1)
{
msg(stderr, "asprintf failed: line %d\n", __LINE__);
exit(1);
}
if(strcmp(action, "unlock") == 0) {
result = lockfile_remove(lockfilename);
} else if(strcmp(action, "lock") == 0) {
if(lockfile_create(lockfilename, retry_count, 0) == L_SUCCESS) {
result = 0;
} else {
msg(stderr, "lockfile creation failed\n");
result = 1;
}
} else if(strcmp(action, "touch") == 0) {
signal(SIGTERM, handle_touchdeath);
if(touchlock_oneshot) {
result = lockfile_touch(lockfilename);
} else {
while(1 && (result == 0)) {
result = lockfile_touch(lockfilename);
sleep(60);
}
}
}
if(lockfilename) free(lockfilename);
return(result);
}
lockfile-progs-0.1.11/lockfile-progs.spec 0000644 0000000 0000000 00000003662 12132611403 0020304 0 ustar 00root root 0000000 0000000 Name: lockfile-progs
Version: 0.1.11
Release: alt2.qa1
Summary: Programs for locking and unlocking files and mailboxes
License: GPLv2
Group: File tools
Packager: Vladimir V. Kamarzin <vvk@altlinux.org>
# http://ftp.debian.org/debian/pool/main/l/lockfile-progs/%{name}_%version.tar.gz
Source: %name-%version.tar
# Automatically added by buildreq on Wed Oct 29 2008
BuildRequires: liblockfile-devel
%description
This package includes several programs to safely lock and unlock files
and mailboxes from the command line.
These include:
- lockfile-create
- lockfile-remove
- lockfile-touchlock
- mail-lock
- mail-unlock
- mail-touchlock.
These programs use liblockfile to perform the file locking and
unlocking.
%prep
%setup
%build
%make
%install
install -d %buildroot{%_bindir,%_man1dir}
cp -a bin/* %buildroot%_bindir
cp -a man/* %buildroot%_man1dir
echo '.so lockfile-progs.1' > lockfile-progs.1
install lockfile-progs.1 %buildroot%_man1dir/lockfile-create.1
install lockfile-progs.1 %buildroot%_man1dir/lockfile-remove.1
install lockfile-progs.1 %buildroot%_man1dir/lockfile-touch.1
install lockfile-progs.1 %buildroot%_man1dir/mail-lock.1
install lockfile-progs.1 %buildroot%_man1dir/mail-unlock.1
install lockfile-progs.1 %buildroot%_man1dir/mail-touchlock.1
%files
%doc TODO debian/changelog
%_bindir/lockfile-create
%_bindir/lockfile-remove
%_bindir/lockfile-touch
%_bindir/mail-lock
%_bindir/mail-touchlock
%_bindir/mail-unlock
%_man1dir/lockfile-create.1*
%_man1dir/lockfile-progs.1*
%_man1dir/lockfile-remove.1*
%_man1dir/lockfile-touch.1*
%_man1dir/mail-lock.1*
%_man1dir/mail-touchlock.1*
%_man1dir/mail-unlock.1*
%changelog
* Mon Apr 15 2013 Dmitry V. Levin (QA) <qa_ldv@altlinux.org> 0.1.11-alt2.qa1
- NMU: rebuilt for debuginfo.
* Tue May 19 2009 Vladimir V. Kamarzin <vvk@altlinux.org> 0.1.11-alt2
- Fix building with gcc4.4
* Wed Oct 29 2008 Vladimir V. Kamarzin <vvk@altlinux.org> 0.1.11-alt1
- Initial build for ALT Linux (spec from PLD)