Entity
Click on the red underlined text to get to the source
... modification time is
not available, either because the pathname identifies no existing
entity or because the information is not available for the entity
named, then a 550 reply should be sent. Where the command cannot be
...
... not available, either because the pathname identifies no existing
entity or because the information is not available for the entity
named, then a 550 reply should be sent. Where the command cannot be
correctly parsed, a 500 or 501 reply should be sent, as specified in
...
...
Where the command is correctly parsed but the size is not available,
perhaps because the pathname identifies no existing entity or because
the entity named cannot be transferred in the current MODE and TYPE
...
... perhaps because the pathname identifies no existing entity or because
the entity named cannot be transferred in the current MODE and TYPE
(or at all), then a 550 reply should be sent. Where the command
cannot be correctly parsed, a 500 or 501 reply should be sent, as
...
... MLST only, a
file name. For these purposes, a "file name" is the name of any
entity in the server NVFS which is not a directory. Where TVFS is
...
... type value, a "parent directory" is any
directory in which there is an entry of type=dir that refers to the
directory in which the type=pdir entity was found. Thus it is not
required that all entities with type=pdir refer to the same
directory. The "unique" fact (if supported and supplied) can be used
...