Samba file timestamp policy with Linux client .vs. Windows client

Samba file timestamp policy with Linux client .vs. Windows client

Post by Richard Conwa » Wed, 03 Mar 2004 19:42:15



I am experiencing a difference in file timestamp behaviour between a Linux
and Windows client accessing a SMB share hosted on a Windows 2003 Server
platform.

Files accessed by the Linux client are left with Modified and Accessed times
based upon the time on the client. Files accessed by the Windows client
(also running Windows 2003 Server) are left with Modified and Accessed times
based upon the time on the *server*. This is causing problems for me as I
have an application running on the server which uses these timestamps to
detect the presence of new or modified files - sometimes file updates are
missed when the update occurs from the Linux client if the system time on
the Linux client is behind that of the server.

Does anyone know if I can configure the SMB client running on the Linux
platform to behave the same as the Windows 2003 SMB client, i.e. I want my
timestamps to be set according to the current time on the server as opposed
to the client.

Thanks,
Richard.

 
 
 

Samba file timestamp policy with Linux client .vs. Windows client

Post by John L. Cunningha » Sat, 06 Mar 2004 01:15:44



> Does anyone know if I can configure the SMB client running on the Linux
> platform to behave the same as the Windows 2003 SMB client, i.e. I want my
> timestamps to be set according to the current time on the server as opposed
> to the client.

NET TIME?

--
John L. Cunningham

 
 
 

Samba file timestamp policy with Linux client .vs. Windows client

Post by Villy Krus » Sat, 06 Mar 2004 17:49:15


On 4 Mar 2004 16:15:44 GMT,


>> Does anyone know if I can configure the SMB client running on the Linux
>> platform to behave the same as the Windows 2003 SMB client, i.e. I want my
>> timestamps to be set according to the current time on the server as opposed
>> to the client.

> NET TIME?

SMB file systems expects time stamp in local time.  Therefore the linux
kernel needs to know the UTC to localtime offset to translate unix
time to localtime.  This doesn't occur automatically, but setting the
timezone information in a call to settimeofdat() would do it (at least on
kernel 2.2).  Remember that the unix and linux kernel does not otherwise
use localtime for anything so failing to set the timezone in the kernel
doesn't affect anything except SMB and VFAT file systems time stamps.

Villy

 
 
 

1. File Server for Windows clients (was: Window NT vs x86 solaris vs SCO?)

The point is well taken that it is more difficult to shoe-horn myriad Windows
clients into the UNIX server's "preferred" file serving protocol--that can be
an administrative nightmare.

Fortunately, as has been pointed out here, that is not necessary.  You can
still have the very best transaction and Internet server (UNIX) and easily
serve files and printing to your Windows/DOS clients.

Note that SCO VisionFS not only available for just SCO OpenServer/UnixWare
or Intel-based systems, but for SPARC Solaris and HP-UX as well.  Ports
for SPARC SunOS, AIX and other UNIXen should be out by year end.

VisionFS also works with other Vision Family products, such as SuperVision,
to help remotely manage all those pesky PCs. ;^)

There is also SCO Advanced File and Print Server for OpenServer Release 5
(Host or Enterprise) systems, which is the actual NT code ported to UNIX.
SCO Advanced File and Print Server comes with NetBEUI, which gives you the
networking you need to tie Windows/DOS desktops to OpenServer.  For those
smaller accounts, a 5-user AFPS + 5-user Host is $1690 U.S. (list prices).

Why SCO VisionFS instead of samba?  Well, it's a fully supported commercial
product with documentation and integrated administration utilities.  And SCO
has done some optimization work to increase performance (and presumably will
continue to do so).

Besides, now that SCO OpenServer (and soon, SCO UnixWare) are *free* for
non-commercial home, educational and evaluation purposes there's no excuse
for not checking out the also free 1-user AFPS "Lite" or the VisionFS demo.

%^)

Regards,

Tim

--
Her sun is gone down while it was yet day.

                                                         --Jeremiah 15:9

2. ip masquerading with RH 7.x

3. dns update from dhcp server ok for windows clients, not ok for linux (dhclient) clients

4. Samba Client/Config Problems

5. Communication needed between linux server/client to windows client/server

6. left button menu desktop

7. dir timestamps vs dir/file timestamps

8. "Linux" under OS/2

9. PPTP client and SAMBA client problem

10. Web client or small client for windows

11. Samba Connection closed between Linux client and Samba server

12. SuSE 7.0 samba client vs. OS/2 machine

13. linux file server and windows based clients