> Michael Halcrow wrote the following on 09/06/2007 08:42 PM: > > To cut a long story short I discovered that the file became garbled > > as soon as the length exceeded 255 bytes, and only when requested > > through the apache web server! > > Then I am inclined to blame some sort of caching in Apache. If you > continue to get this behavior after completely shutting down Apache > and wiping its cache, then it's time to start considering that there > is an obscure corner case where eCryptfs is passing through the lower > inode mapping, but we need to entirely rule out any remaining cache in > Apache first. I rebooted the system and am still observing the same behavior. Note that I can toggle the behavior on and off by adding or removing an extra character to the file. I have the file open in emacs and retrieves it using wget (to avoid any web browser caching).
Strange it is. I need to try your suggestion about using strace, but that may have to wait a day or two. -- Stefan Farestam Mobile: +46 70 649 6838 ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ eCryptfs-users mailing list eCryptfs-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ecryptfs-users
