On 05/15/98 14:39:03 you wrote:

We recently observed some strange behavior due to the filer's clock being about 1 minute and 30 seconds faster than a client's. The dates displayed by 'ls -l' of files that had been recently created were listed as "May 14 1998" instead of "May 14 18:22" like they should be.

That is odd... I though ls did this only if the file was older than six months. I presume after 90 seconds it displays normally again, so I guess the ls in question isn't handling "in the future" times very well (it thinks they are in the past).

It is important that NFS clients and servers have the same time. We would prefer to use NTP for time synchronization on the NetApp instead of running a cron job on a UNIX server that will fire off a 'rsh rdate' command on the filer.

It is a little bit of a hassle, but rsh rdate works pretty well. Any reason why you don't want to use it? Do you use NTP for the rest of your environment?

Does anyone know about any NetApp plans to support NTP?

I've heard a lot of people ask for it over the years but usually they move on to a different solution since HTP doesn't seem immediately forthcoming.

Bruce