SAMBA digest 1588

[Richard Colley]

I'm confused.  Why has the VC++5.x problem only started occurring in
1.9.18x.

We have successfully been using VC5 with 1.9.17p4 for some time with no such
problems.
So, what's differrent between 1.9.17 & 1.9.18 that caused this problem to
manifest itself?

TIA

Richard

>
>Date: Wed, 11 Feb 1998 11:17:45 -0800
>From: Jeremy Allison <jallison at whistle.com>
>To: hague at research.canon.com.au
>Subject: Re: Directory ctimes
>Message-ID: <34E1F959.33590565 at whistle.com>
>
>Jim Hague wrote:
>
>>
>> Unix time semantics here don't exactly match Win32, so Samba reports the
>> ctime as the creation time, which is fair enough. Unfortunately, when an
SNIP
>This is a really interesting post, as I've been working on the VC++5.x
>problem for 1.9.18p3.
SNIP
>One of the other issues is getting around the hideous
>'file changed' bug - which seems to be triggered by
>code in VC++ working around a Win95 server bug. As
SNIP
>I'm adding an option for p3, "win95 bug compatibility"
>which causes Samba to return mtime for atime, and
>swap the byte order of a date in one return call
>(as Win95 does) - this seems to make the problem
>much better (although it does still occasionally
>occur).