File change notification every time I write to a network drive

tatacalu · 09-08-2009, 07:21 AM

Hello!

I have a relatively common problem, but I don't seem to identify it's source.
I have a SAMBA server on my LAN to which there are mapped a few shares as network drives in windows xp (as Y

and mounted as CIFS in linux [as /y].

The problem is that every time I save a file [either windows xp or linux] on the mapped drive / mounted folder, our IDEs alert us that the file changes right after the save.

I am running SAMBA 3.3.2.

Does anyone please have any idea ?

estabroo · 09-09-2009, 08:26 AM

I'd guess you have clock skew between your machines and your server.

tatacalu · 09-09-2009, 08:41 AM

THANK YOU SO MUCH !!!!

I would have never thought about that, you are a lifesaver!

I opened the services GUI and I saw that on the client machine the ntpd wasn't started.

I also saw that there are 2 services:
ntpd => /etc/init.d/ntpd
ntpdate => /etc/init.d/ntpdate

Can anybody tell me what is the difference between them ? [or maybe point me to a link where that is explained?]
As far as i know, ntpd is the NTP daemon, so ntpdate is.... another daemon ?

Thank you again !!!

estabroo · 09-09-2009, 08:48 AM

ntpdate is for one-shot updates to your clock, generally run before starting ntpd since ntpd doesn't keep a clock in sync if it is already outside its acceptable differential. You can also run ntpdate manually doing something like ntpdate -u name.or.ip.of.ntp_server

tatacalu · 09-09-2009, 08:51 AM

ok, I knew taht you could manually call ntpdate to keep the clock in sync, but what I don't understand is why there is a daemon [service] ntpdate... if it is used for one-shot updates.

estabroo · 09-09-2009, 12:12 PM

On your system it probably has a service entry so that your clock gets in sync before the ntp daemon is started.