GNOME Bugzilla – Bug 434676
Errors when there is a symlink to .beagle/TextCache
Last modified: 2007-05-16 20:33:40 UTC
Please describe the problem: I have a symlink from .beagle/TextCache to /somewhere/else/TextCache Beagle produces many error messages that look like this: System.IO.DirectoryNotFoundException: Could not find a part of the path "<Home>/.beagle/TextCache/86". at System.IO.FileStream..ctor (System.String name, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, Boolean anonymous, FileOptions options) [0x00000] at System.IO.FileStream..ctor (System.String name, FileMode mode, FileAccess access, FileShare share) [0x00000] at (wrapper remoting-invoke-with-check) System.IO.FileStream:.ctor (string,System.IO.FileMode,System.IO.FileAccess,System.IO.FileShare) at Beagle.Daemon.TextCache.GetWriter (System.Uri uri) [0x00000] at Beagle.Daemon.TextCache.WriteFromString (System.Uri uri, System.String str) [0x00000] at Beagle.Daemon.TomboyQueryable.TomboyQueryable.PostAddHook (Beagle.Indexable indexable, Beagle.Daemon.IndexerAddedReceipt receipt) [0x00000] at Beagle.Daemon.LuceneQueryable.HandleAddReceipt (Beagle.Daemon.IndexerAddedReceipt r, Beagle.Indexable indexable) [0x00000] at Beagle.Daemon.LuceneQueryable.Flush () [0x00000] These error messages do not occur when TextCache is directly contained within .bealge (without a symbolic link). Steps to reproduce: Actual results: Expected results: Does this happen every time? Yes. Other information:
I could not reproduce the problem. Are you sure symlink is correct i.e. can you manually cd to "cd ~/.beagle/TextCache/86" ?
OK -- I just did the following: 1) shutdown the beagle demon 2) cd .beagle mv TextCache /somewhere/else ln -s /somewhere/else/TextCache 3) restarted the beagle demon Everything seems to work now. This is version 2.16.3.ubuntu4 -- maybe this has been fixed in the meantime? I was pretty sure that this was not a broken link, since I tried this several times before I gave up and reported the original bug, but who knows, maybe I messed up several times in a row -- sorry if that was the case. Seems this can be closed.
Hmm... I dont remember anything changing. Who knows what was wrong! Since it is working now, I am closing this bug. Please reopen if the problem reappers.