Can't think of anything off the top.
If you're familiar with CIFS, you might want to look at a network trace to
see if the timestamps returned over the wire are correct. You might also
get an idea of when things start going wrong and why. For example, is it
Samba or the DFS client that is the culprit.
Have you tried this with an NT DFS server?
I'll try and reproduce this when/if I can..
- SK
-----Original Message-----
List: samba
Subject: [Samba] Directory Timestamp Problem in Dfs Root
From: "John P Janosik" <jpjanosi@us.ibm.com>
Date: 2002-04-10 22:48:52
I think I may have found a problem with the time/date stamp Samba is
returning for Dfs links.
We are running Samba 2.2.3a built with the --with-msdfs config option on a
RedHat 7.2 linux machine. Right now the only share we have is a Dfs root
that contains a few thousand Dfs links. When we do a "dir" in a
command
prompt mapped to that drive only the first 160 links show the correct
time/date stamp. If I do a "dir" to a drive mapped to another Samba
server
that contains a few thousand real directories the time stamps all look
correct. Here is an excerpt of the directory listing:
03/28/2002 11:36a <DIR> hillier
03/28/2002 11:36a <DIR> jeffg
03/28/2002 11:36a <DIR> kaba
03/28/2002 11:36a <DIR> sloneker
03/28/2002 11:36a <DIR> v1voss
12/23/1935 02:39a <DIR> gardinor
12/23/1935 02:39a <DIR> johnthom
12/23/1935 02:39a <DIR> mcurrie
12/23/1935 02:39a <DIR> markpf
12/23/1935 02:39a <DIR> eschmitt
I have a few log files at various debug levels but I cannot see anything
obviously failing.
Thanks for any suggestions,
John Janosik
jpjanosi@us.ibm.com