Gentlemen;
We have several windows based applications that reference a logical drive (i.e.: F:\) that is actually an smb link to a file in a directory on an AIX 5.1L system running samba version 2.2.1
What we are experiencing is that if a file on the samba drive is updated, the logical drive on the Windoze machine points to the OLD version. The only way to resolve this is to drop the connection then re-map the connection. This appears to be true if the file is edited by a Windoze program OR an aix program.
When we asked about this some time ago someone recommended the following line be added to our smb.conf file which we did:
> socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
However, it didn't seem to resolve our issue.
Can anyone comment on or provide a means to allow our logical drive to reflect the "current state" of the actual drive file(s)?
Thanks all,
Bob
We have several windows based applications that reference a logical drive (i.e.: F:\) that is actually an smb link to a file in a directory on an AIX 5.1L system running samba version 2.2.1
What we are experiencing is that if a file on the samba drive is updated, the logical drive on the Windoze machine points to the OLD version. The only way to resolve this is to drop the connection then re-map the connection. This appears to be true if the file is edited by a Windoze program OR an aix program.
When we asked about this some time ago someone recommended the following line be added to our smb.conf file which we did:
> socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
However, it didn't seem to resolve our issue.
Can anyone comment on or provide a means to allow our logical drive to reflect the "current state" of the actual drive file(s)?
Thanks all,
Bob
