On Mon, Oct 10, 2005 at 07:59:48PM -0500, Craig A. Berry wrote: > At 10:41 PM +0100 10/10/05, Nicholas Clark wrote: > > > >I mailed the testdrive support folks, and they say that they don't attempt > >to synchronise the clocks on the VMS clusters. Their simpler recommendation > >was to not build across the cluster, which means that I need to work out > >which (if any) machines have filespace accessible to me that is on the local > >machine. > > It looks like all the user disks are served up from spe180, which is > in fact a few seconds ahead of spe183.
I've tried on user1 and user5 on spe180, and I'm still getting the same errors. I don't know how to do this from the native VMS shell, but the bash version of things looks wrong: bash$ date Tue Oct 11 04:09:11 EDT 2005 bash$ touch foo bash$ ls -l foo -rw-r----- 1 NWC10 129 0 Oct 11 03:09 foo bash$ date Tue Oct 11 04:09:30 EDT 2005 3am vs 4am makes me think that there's something rather more screwed than a few seconds drift. Or is this something wonky with ls returning a result in wintertime, and date giving a date in summertime? Only that's *D* which is wintertime, isn't it? Nicholas Clark
