Endian Bugtracker
Endian Issue Tracker





Please see now our new Bugtracker system: JIRA








View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0002644Endian FirewallOther Scriptspublic2010-01-28 15:282010-09-21 20:33
Reporterpeter-endian 
Assigned To 
PrioritynormalSeverityminorReproducibilityrandom
StatusconfirmedResolutionopen 
PlatformOSOS Version
Product Version 
Target VersionfutureFixed in Version 
Summary0002644: synchronization issues in endian.core.notification module
DescriptionStatusFileMutex.__init__() removes the mutex file if it does already exist
StatusFile.close() removes the mutex file after releasing the lock.

what if another process (B) acquired a lock on the mutex file held by process A? That process stored already the filehandle and blocks until A releases. When process C removes the file, before acquire(), C can create a new file which is not more blocked by A. The file blocked by A is removed from the filesystem, but the filedescriptor is still open and A can write to it.

When A closes that filedescriptor, process B will be able to open it and continue operations on it. But that is not more the same file as we see in the filesystem.

In that case 2 processes with the same lockfile are running but only 1 lockfile is visible in filesystem.

That's no mutex
TagsNo tags attached.
Attached Files

- Relationships

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2010-01-28 15:28 peter-endian New Issue
2010-09-21 20:33 peter-endian Status new => confirmed

Copyright © 2005-2008 Endian, SRL. All rights reserved.


Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker