dbf in Linux NFS mounted directory

[Daniele Campagna]

Hi all, I was testing a program (under Linux) and ran it ("box 1") in a
NFS mounted directory, a directory on another Linux box, ("box 2")
exported via exportfs and mounted on "box 1".

Despite the directory has the right permissions (in "box 2"), append
blank failed.

After some other tests, it seems that Harbour complains about record
locking failed.

Has someone had the same issue?

Dan

[do...@people.net.au]

Hi Dan

The short answer is no it all just ran fine for me even with the NFS mount across a VLAN.

Across the VLAN it was rather slow so rewrote it as a client server application.

I assume you can write to files on "box2" and have tested that.  If so I am at a bit of a loss as to what to suggest.

Regards
Doug



On Tue 17/01/17 12:55 , Daniele Campagna cyber...@tiscalinet.it sent:

--
--
You received this message because you are subscribed to the Google
Groups "Harbour Users" group.
Unsubscribe: harbour-users+unsub...@googlegroups.com
Web: http://groups.google.com/group/harbour-users">http://groups.google.com/group/harbour-users

---
You received this message because you are subscribed to the Google Groups "Harbour Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to harbour-users+unsub...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Daniele Campagna]

Thanks Doug, no VLAN here, just 2 Slackware boxes, one of them virtualized  via VMPlayer and the other native (slackware 12.2 vs. slackware 13.37/64). Not a big issue, but after your answer I feel encouraged to investigate more. Yes, "box 2" reads/writes regularly to the mounted directory (exported from Slack 13.37). Recompiled dbu hangs either... puzzling.

Maybe it's a problem tied to different kernel versions, or my complex setup. I'll try with another Linux box. Ah, with Windows (virtualized or native), accessing the same directory via Samba, there are no problems ("box 2" shares via Samba that directory, while the root filesystem is exported via exportfs to "box 1") ... maybe this is the problem, the Samba share somewhat interferes with the locking mechanism.

Dan