After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 343366 - Beagle does not clean up lock files at startup
Beagle does not clean up lock files at startup
Status: RESOLVED FIXED
Product: beagle
Classification: Other
Component: General
0.2.6
Other Linux
: Normal normal
: ---
Assigned To: Beagle Bugs
Beagle Bugs
: 350520 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-05-30 07:39 UTC by Nicolas Maquet
Modified: 2006-08-09 15:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description Nicolas Maquet 2006-05-30 07:39:46 UTC 
It seems that beagle does not clean up ".lock" files in the .beagle directory.

Those are found in : 

~/.beagle/Indexes/GaimLogIndex/Locks
~/.beagle/Indexes/TomboyIndex/Locks
~/.beagle/Indexes/FileSystemIndex/Locks
... etc.

The problem is that when beagled is shutdown unproperly (kill -9), the .lock files stay, resulting in "Lock obtain timeout" exceptions (see bug 340542).
The only way to get beagle out of this situation is to remove the .lock files *by hand*... Should'nt beagle just remove all its lock files at startup ?
Comment 1 Joe Shaw 2006-05-31 18:48:22 UTC 
Fixed now in CVS.
Comment 2 Sam Morris 2006-06-05 10:57:37 UTC 
If the locks are removed at startup then what happens if I log in to a machine twice? Are the lock files belonging to the first instance of beagled removed by the second?
Comment 3 Nicolas Maquet 2006-06-05 11:02:14 UTC 
> If the locks are removed at startup then what happens if I log in to a machine
> twice? Are the lock files belonging to the first instance of beagled removed by
> the second?

I don't think so, beagle is clever enough not to launch a second deamon process when one is already present. 

nmaquet@AmaNiX:~$ ps -A | grep beagle
 4984 ?        00:00:30 beagled
 6058 ?        00:00:01 beagled-helper
nmaquet@AmaNiX:~$ beagled
nmaquet@AmaNiX:~$ ps -A | grep beagle
 4984 ?        00:00:30 beagled
 6058 ?        00:00:01 beagled-helper
nmaquet@AmaNiX:~$
Comment 4 Joe Shaw 2006-08-09 15:44:22 UTC 
*** Bug 350520 has been marked as a duplicate of this bug. ***