--
--
You received this message because you are subscribed to the Google
Groups "Harbour Users" group.
Unsubscribe: harbour-user...@googlegroups.com
Web: 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-user...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Hi Anthony,
On Jun 12, 2013 9:36 AM, "Anthony Smith" <ant...@gmail.com> wrote:
>
> Hi Teo,
>
> I'm using Linux and Windows, but can easily use only Linux or only Windows (preferably Linux)
> I tried NFS, but could not get record locking, reading, adding files and deleting them was fine, but it hung when adding / updating a record.
> I think I have to look at NLM, perhaps that will solve my problem.
>
So if you can chooose, then I strongly recommend you to use Linux for simplicity and efficiency.
No need of Samba/NFS/NLM.
You only need to configure your clients to access the Linux server via ssh or telnet.
> hbnetio seems interesting, do you have any experience with it, perhaps a sample piece of code?
>
I have hbnetio running on some networks were clients can be any of Linux, Windows and MacOS. And hbnetio works very efficient and without any trouble.
You'll find a comprehensive sample of hbnetio somewhere in the harbour tree.
Best regards,
Teo
# Samba Config
# Global Settings
[global]
workgroup = WORKGROUP
netbios name = MYSERVER
server string = Samba Server %v
security = user
dns proxy = no
# No password required
map to guest = bad password
# Share Definitions
[documents]
comment = Letters and family history path = /data/documents browsable =yes writable = yes guest ok = yes read only = noHi Anthony,
I've run into similar problem before. Try to look into samba configuration documentation about file locking. You should disable samba file locking. And in your code you should lock the file or record before making any modification to dbf file.
Regards,
Anes
you got various suggestions but some are really unrelated and propose different scenarios and use cases!
Anyway, i've been using linux+samba with windows clients for over 10 years and experienced problems only twice....
Hi,
caching at server side is good (when it run reliable).
Read- or write- Caching at client (user) side is B_A_D in case of a SHARED DATABASE application
- typical results are missing data, destroyed index etc.
Mounting a Samba share in Linux client you can 'turn off' the cache with mount option:
cache=none
i.e.:
mount -t cifs -o cache=none,username=YourSambaUser //server/share /mnt/point
The default status of this cache behaviour seem different at different Linux distros,
newer distro seem enable cache. Fully DISabling it explicitely you are on the safe side.
There exist also the setting: cache=strict or strictcache, which plays with
"oplocks=" and "level2 oplocks=" Samba settings
- maybe an improvement option for later, but i'm unsure
-- see for doc mount.cifs and try on own risk.
---
It is often recommended to turn off opportunistic locking, which should in turn turn off
caching for Windows clients.
You can try this with already mentioned setting: oplocks = no
in your Samba (smb.conf) configuration and hope that Windows reacts correctly.
I astonished found a Harbour function: Win_OSNetRegOK( lSetIt, lAstaLaVista ;)
in the hbwin contrib, which sets some registry keys for you.
And on this site ( thanks! Klas ) you find registry files - see the good comments therein.
http://www.witzendcs.co.uk/nt_networking.html
Regards
Rolf