process-upload lockfile has bad permission
Bug #52025 reported by
Malcolm Cleaton
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Medium
|
Celso Providelo |
Bug Description
We hit a problem today with Soyuz, after a reboot of drescher; a lockfile was left lying around with permissions such that only one of the relevant lp_* users could play with it.
We use file-locking for our locking, so that locks will automatically be released when things crash hard, but this doesn't help if the lockfiles don't have the right permissions. We need to ensure we create lockfiles with sufficient write access for all users who share the lock, so that hard crashes won't require manual lock frobbing.
Changed in soyuz: | |
assignee: | nobody → malcolmcleaton |
importance: | Untriaged → Medium |
status: | Unconfirmed → Confirmed |
To post a comment you must log in.
I'm taking the liberty of unassigning Malcolm from this, as I doubt he's going to be working on it any more.
This is biting us in process-upload at the moment. How about:
--- process- upload. py.orig 2007-02-10 12:44:58.000000000 +0000
+++ process-upload.py 2007-02-10 12:45:24.000000000 +0000
@@ -28,7 +28,9 @@
options = readOptions()
log = logger(options, "process-upload")
+ old_umask = os.umask(0002) _default_ lockfile, logger=log)
locker. acquire( ) ired:
locker = GlobalLock(
+ os.umask(old_umask)
try:
except LockAlreadyAcqu