0000705: Creating files on an NFS-mounted directory does not honor the current time when redirecting

Notes
(0001090) landley 02-13-06 23:41	Wait, you're seeing different behavior between "cat file > foo" and "echo blah > foo"? How does that work? In both cases the file is created by the > before the command to the left of it even gets _run_, so that _can't_ distinguish between different command being run because the command isn't run until afterwards. In any case, the timestamp on a freshly created file is a function of the operating system. In the case of an NFS server, the creation time may be the time according to the _server_, not the machine you have that filesystem mounted on. (Since the actual file creation operation is done by the nfs server, not by the client.) If those two are way out of sync with each other, that's not busybox's problem. Touch explicitly sets the file's time to the current system time via utime(), so that'll set the time from the client's point of view even if the server is off in la-la land. But normal file creation just does an open() and leaves time setting to the operating system. If that isn't setting the file's time right, that's not busybox's fault.

(0001091) landley 02-13-06 23:42	Check the clock on your NFS server.

Relationships