Open Bug 719654 Opened 12 years ago Updated 2 years ago

Detect previous start-up failure (symlink fallback case)

Categories

(Toolkit :: Startup and Profile System, enhancement)

All
Linux
enhancement

Tracking

()

People

(Reporter: MattN, Unassigned)

References

Details

See bug 294260 comment 41:
> * This doesn't detect startup crashes if the profile is using symlinks (rather 
> than fcntl) as the primary locking mechanism.  This is because replacedLockTime 
> requires that the existing lock is still on disk but not unlinking the symlink 
> would cause profile locked messages.  A possible workaround is to change the 
> symlink during an expected shutdown so that it is detected as stale on next 
> startup.  My understanding is that only a small proportion of users will be 
> relying on symlinks since the fallback is for old NFS servers that don't support 
> fcntl.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.