>> -r-------- 1 frederik frederik 6 2009-01-11 17:23 >> /home/frederik/.beagle/Indexes/IndexingServiceIndex/Locks/lucene-87e2d2d7eab46d37e08cb23db1c76b0c-write.lock >> >> Making the file writeable again, fixed the problem. I have no idea >> how these permissions got screwed up. > > Was looking and my logs last night and this had happened on my setup > too. Not sure why.
Probably related to this: http://svn.gnome.org/viewvc/beagle?view=revision&revision=4897 "File.Delete requires write permission on the file! This is different than the POSIX behaviour and this bug was fixed in mono recently. As a result, with mono-2, beagle tmpfiles could not be deleted. Workaround this problem by using the Mono.Unix Unlink syscall." Lockfiles are created readonly (not sure what goes wrong if we create them read-write). r4897 fixed the most common branch when a lockfile could be deleted but we missed the directory delete possibility: System.IO.File.Delete System.IO.Directory.RecursiveDelete System.IO.Directory.Delete Beagle.Daemon.LuceneCommon.Create I will try to look into this when I get some time. - dBera -- ----------------------------------------------------- Debajyoti Bera @ http://dtecht.blogspot.com beagle / KDE fan Mandriva / Inspiron-1100 user _______________________________________________ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
