At times, misconfigured Samba may not report timestamps at all.
On Wed, Oct 19, 2011 at 8:55 AM, Stephan Beal sgbeal@googlemail.com wrote:
On Wed, Oct 19, 2011 at 4:42 PM, Frank Lanitz frank@frank.uvena.dewrote:
Am 19.10.2011 16:29, schrieb John Beaumont | Beecroft:
Changing the disk check timeout to zero remedies the sporadic messages but I still get a warning on every save. I assume geany is just going on the modification timestamp which always appears to be 1 second out. The server's clock and my client's clock are synchronised although this shouldn't matter anyway.
if i'm not sorely mistaken, CIFS/SMB historically has problems with precise timestamps. This article:
http://www.obdev.at/resources/sharity/manual3/en/singlepage.html
claims +/- 2 seconds.
-- ----- stephan beal http://wanderinghorse.net/home/stephan/
Geany mailing list Geany@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany