I was about to file a new bug report for a similar problem, so I'm updating this one instead.
I've noticed locking problems when I want to open LO files stored on my Synology NAS, exported via NFS. I ran LO from Linux Ubuntu clients (15.10).
When trying to open a file on the NFS server, LO shows an error message (after about 30 seconds, probably a timeout) and proposes to open the file read-only or to open a copy.
I "solved" the problem by rebooting the NAS, but it re-occurs after some time.
I've just given a quick look at LO sources, and noticed that in sal/osl/unx/file.cxx (openFilePath), locks are acquired using fcntl(F_WRLCK), but I couldn't find code to unlock the file.
There is support to unlock files in sal/osl/unx/profile.cxx (OslProfile_lockFile), but I don't know if it's actually used.
My assumption is that LO could keep acquiring locks, never releasing them, until the NAS is out of resources.
I was about to file a new bug report for a similar problem, so I'm updating this one instead.
I've noticed locking problems when I want to open LO files stored on my Synology NAS, exported via NFS. I ran LO from Linux Ubuntu clients (15.10).
When trying to open a file on the NFS server, LO shows an error message (after about 30 seconds, probably a timeout) and proposes to open the file read-only or to open a copy.
I "solved" the problem by rebooting the NAS, but it re-occurs after some time.
I've just given a quick look at LO sources, and noticed that in sal/osl/ unx/file. cxx (openFilePath), locks are acquired using fcntl(F_WRLCK), but I couldn't find code to unlock the file.
There is support to unlock files in sal/osl/ unx/profile. cxx (OslProfile_ lockFile) , but I don't know if it's actually used.
My assumption is that LO could keep acquiring locks, never releasing them, until the NAS is out of resources.
Is that plausible?