On 11/24/20 2:18 AM, Stephen Morris wrote:
On 24/11/20 1:55 pm, Richard Kimberly Heck wrote:
On 11/23/20 9:17 PM, Jonathan Billings wrote:
On Nov 23, 2020, at 19:05, Richard Kimberly Heck <rikiheck@xxxxxxx>
wrote:
LyX refuses to start, blocking at a call to
lockf(fd, F_LOCK, 0) at support/filetools.cpp, during startup. (I
believe that fd here points at a file on the NFS share.)
Did you end up using NFSv4? It sounds like a locking problem but
the implementation differs significantly between v3 and v4.
I believe it is v3 on the server. If I specify nfs4 as the filesystem
type, then I get:
mount.nfs4: mounting 192.168.1.2://home/photos/ failed, reason given
by server: No such file or directory
The directory exists, so I guess it must not be exported that way.
Here's the relevant portion of /etc/fstab on the client:
192.168.1.2://home/rikiheck/files /home/rikiheck/files nfs
auto,nouser,rw,dev,nosuid,exec,_netdev 0 0
192.168.1.2://multi/ /mnt/mail/multi nfs
auto,nouser,rw,dev,nosuid,noexec,_netdev 0 0
192.168.1.2://home/photos /mnt/mail/photos nfs
auto,nouser,rw,dev,nosuid,noexec,_netdev 0 0
Riki
I think Fedora uses nfs version 4 by default. As one of the options I
think you can specify nfsver=3 which should cause Fedora to use
version 3 of nfs, which might resolve your issue. I have a nas disk
which uses nfs version 1 and I have had to specify nfsver=3 to mount it.
Thanks for the suggestion. Unfortunately, while it didn't hurt, it
didn't help, either.
Riki
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
