On Mon, Nov 13, 2006 at 10:22:21PM -0200, [EMAIL PROTECTED] wrote: > What I am sure about is that setting HOME environment variable to a > directory not located over NFS and then executing listen does not get me > that error. And I have setups where my home is not over NFS and listen > works OK.
What happens if you first move away your .listen directory? It's entirely possible that yours became corrupt for some reason and mine didn't. > Or perhaps there is something about our NFS server setup. Mine was using > the kernel server, because it has lock support (and its lack would be the > first thing I would point as the reason for the errors). I'm using the NFS kernel server, too. I don't think anybody uses the NFS user server anymore; it hasn't been developed for years either. > Any tests I can try? The setup is on a lab which I may have some remote > access (I will not be there until next week). In general, I'd try to isolate if this is a feature of your NFS setup in general, or your specific .listen directory (probably media.db). What happens if you copy the .listen directory to somewhere on non-NFS, set $HOME to that place and the run listen? Also, does this happen _every_ time or can you run listen a few times before the database goes bonkers? You don't access the database from multiple hosts at the same time, do you? /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
