Hi,
this is a one-time post to announce the creation of "withlock" - a locking wrapper script to make sure that some program isn't run more than once. It is ideal to prevent periodic jobs spawned by cron from stacking up. The locks created are valid only while the wrapper is running, and thus will *never* require additional cleanup, even after a reboot. This makes the wrapper safe and easy to use, and much better than implementing half-hearted locking within scripts.
Usage is simple. Instead of your command
CMD ARGS...
you simply use
withlock LOCKFILE CMD ARGS...
If you are a mirror admin, there is a 99.9% chance that you might want to use this locking wrapper. Likely you ran into the situation where a script was (unexpectedly...) not finished before it was started another time; and/or you actually hacked some kind of locking into a script to prevent that from happening.
Since I suffered the same situation for some years, I looked around for solutions, and since I couldn't find one, I finally took the time to create one. The resulting wrapper is used in production since summer 2009, and proved to work reliably. Put the wrapper around all your cron jobs and be happy :-)
Home page: http://code.google.com/p/withlock/
Features:
- locks that never need a cleanup, whatever might happens
- can wait a defined time for a lock to become "free"
- makes sure that lock files aren't created in unsafe locations (to prevent symlink attacks)
- easily installed (it's just one file), highly portable
Requirements:
- Python 2.4 or newer
- lots of platforms are supported (see list on home page)
For more information, please come to http://code.google.com/p/withlock/ .
Thanks,
Peter
PS. Apologies when you receive this mail more than once, due to crossposting to some forums where to reach most people--
To unsubscribe, e-mail: mirror+unsubscribe(a)opensuse.org
For additional commands, e-mail: mirror+help(a)opensuse.org
I've already pulled about 30GB today, much of it in factory-snapshot.
Is it normal? I'd expect the milestone to be in other paths.
--
To unsubscribe, e-mail: mirror+unsubscribe(a)opensuse.org
For additional commands, e-mail: mirror+help(a)opensuse.org
When using rsync to get a list of files (which means --list-only is
either given or implied) from
stage::opensuse-full-really-everything/opensuse we get this:
lrwxrwxrwx 8 2009/10/29 06:26:06 distribution/11.2/repo/oss/boot/i386/branding
lrwxrwxrwx 8 2009/06/16 22:46:03 factory-snapshot/repo/oss/boot/i386/branding
lrwxrwxrwx 8 2009/06/16 22:46:03 factory/repo/oss/boot/i386/branding
Note the difference in timestamps between the first and the other two.
*However* all 3 files are hardlinks to the same inode, as shown by
ls -i:
2147487511 distribution/11.2/repo/oss/boot/i386/branding
2147487511 factory-snapshot/repo/oss/boot/i386/branding
2147487511 factory/repo/oss/boot/i386/branding
All file creation and updates are done by rsync, which means it's
rsync that is creating the hardlinks. Therefore there is a
contradiction between what rsync does with the files and its own
listing.
The problem has been going on for weeks. It also happens with
initrd-xenpae and vmlinuz-xenpae in the same directory and in the
x86_64 one. BTW, they're all hardlinks to inodes that are symlinks.
In order to see if this bug is due to rsync I'd like to see a listing of
these files produced by something like ls -li, find or stat. Please
post it here.
--
To unsubscribe, e-mail: mirror+unsubscribe(a)opensuse.org
For additional commands, e-mail: mirror+help(a)opensuse.org
Hi,
Not to loose time I'm uploading Milestone2 today.
Greetings, Stephan
--
To unsubscribe, e-mail: mirror+unsubscribe(a)opensuse.org
For additional commands, e-mail: mirror+help(a)opensuse.org
I do not know if anybody still cares about the 10.3 update tree, but I
got a report from user about "missing files":
$ find -L update -type l
update/10.3/rpm/src/libpurple.spm
update/10.3/rpm/src/fetchmailconf.spm
update/10.3/rpm/src/openldap2-back-meta.spm
update/10.3/rpm/src/xemacs-info.spm
update/10.3/rpm/src/xemacs-el.spm
update/10.3/rpm/src/libtiff3.spm
Would be nice if those symlinks could be deleted or linked to existing
files.
Adrian
--
To unsubscribe, e-mail: mirror+unsubscribe(a)opensuse.org
For additional commands, e-mail: mirror+help(a)opensuse.org