Comments inline.

On Sat, Jan 04, 2003 at 06:45:51PM -0500, Gene Heskett wrote:
> 
> I've been told, and have repeated here, that the mtimes of a file 
> are not supported by samba because they are not supported by the 
> underlying (usually vfat) file system.  So apparently, some dummy 
> value gets plugged into that field, and if it changes, you get the 
> message.

Hey Gene,

        Actually, this is an ffs (native OpenBSD) partition.

> In a roundabout way, this also explains why a samba share will often 
> get a level 1 that looks like a level 0 sizewise.  I also have one 
> non-samba, small dos partition for holding bios flash images and 
> such, and it gets a full every night, apparently for this same 
> reason.  Minor detail in that case as its less than 20 megs.
> 
> This to me, if its all true, is the one major achilles heel of 
> samba.
> 
> I keep my music on an ext3 partition :-)

        I can easily blame Samba; I think it's a reasonable assumption
to say that Samba is "touching" the files somehow.  However, that goes
right out the door, when I add that this server has _three_ other
Samba shares, on the same type of filesystem, that do _not_ have this
annoyance.  Now, how do we explain THAT?

        Thanks very much for your email...  I'd appreciate any further
thoughts.  :)  This is very perplexing.

Benny


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Discharge of a nuclear weapon shall be deemed a warlike act,
even if accidental."       -- My homeowners insurance policy