|Reported by:||lesd||Owned by:|
|Keywords:||Cc:||lesd, Tim Kosse|
|Component version:||Operating system type:|
|Operating system version:|
Quote from codesquid from an earlier bug report
MDTM cannot be used to set file timestamps.
Example: MDTM 20050726131800 foobar
What does this command do? Set timestamp for the file
'foobar' or get timestamp for the file '20050726131800
Due to this conflict, MDTM should only be used to get
This is a feature that I badly need and have been
assured that many other FTP Servers do implement it.
Surely the ambiguity is only there if a file of that
name *does* exist. If not then can FZ not accept the
command as a request to update the timestamp?
In addition, the likelyhood of having such a filename
must be so remote that the default should be to update
file 'foobar' with what is a valid timestamp and only
if the file does not exist should FZ try to find a file
with name '20050726131800 foobar' and return its
Please could you re-consider, as this feature would
make the life of synchronization programs so much
simpler and more reliable.