It's funny you should comment on this - I was in the middle
of moving to the Samba4 way of handling times and timezones
(back porting the Samba4 code to Samba3) to fix the timezone
problems people have. I was planning to get this into 3.0.21.
Would this fix the problem ? I'm expecting so,
It's funny you should comment on this - I was in the middle
of moving to the Samba4 way of handling times and timezones
(back porting the Samba4 code to Samba3) to fix the timezone
problems people have. I was planning to get this into 3.0.21.
Would this fix the problem ? I'm expecting so,
The way it works now in the sources, Samba goes out of its way
to force Windows clients to see the file times the way Unix and
other more mature systems see them. If a file was modified at
noon 12:00:00 of any day, it shows 12:00:00 always, regardless
of the date on which it was modified or
Surprisingly few threads on this fascinating subject!
(They're all in the Cc:) Only one solution proposed by Thomas
Honigman and Thomas Guenther. In a posting of Feb 8, this year,
they proposed conditioning the use of kludge GMT, which is
what Samba marshals on the wire as GMT but which is
On Fri, Nov 04, 2005 at 10:04:04PM +0100, Dragan Krnic wrote:
Surprisingly few threads on this fascinating subject!
(They're all in the Cc:) Only one solution proposed by Thomas
Honigman and Thomas Guenther. In a posting of Feb 8, this year,
they proposed conditioning the use of kludge GMT,
On Fri, 4 Nov 2005, Dragan Krnic wrote:
The way it works now in the sources, Samba goes out of its way
to force Windows clients to see the file times the way Unix and
other more mature systems see them. If a file was modified at
noon 12:00:00 of any day, it shows 12:00:00 always, regardless
On Fri, Nov 04, 2005 at 01:05:30PM -0800, Jeremy Allison wrote:
It's funny you should comment on this - I was in the middle
of moving to the Samba4 way of handling times and timezones
(back porting the Samba4 code to Samba3) to fix the timezone
problems people have. I was planning to get
