[jcifs] RE: That SMB_COM_CLOSE thing...

[Allen, Michael B (RSCH)]

I'll create a new jar with a copyTo() that uses SMB_COM_COPY in a minute.

But here's something else that looks like it might be broken. You're supposed to be able to specify a
UTIME in SMB_COM_CLOSE of the "Time of last write". I just tried it with NT4 and it didn't work. It
uses the current time regardless.

I've prepared a jar that illustrates this behavior. If you use the CopyTo example it will submit the last
modified time of the source file in the SMB_COM_CLOSE operation for the destination file (to save a
setattr in light of no SMB_COM_COPY). You can see it in the trace. But when you look at the time in
Explorer of the new file it has the current time.

  http://users.erols.com/mballen/jcifs-0.7.0bCloseTime.jar

> -----Original Message-----
> From:	Christopher R. Hertel [SMTP:crh at ubiqx.mn.org]
> Sent:	Monday, August 19, 2002 10:18 PM
> To:	Allen, Michael B (RSCH)
> Cc:	jcifs at samba.org
> Subject:	That SMB_COM_COPY thing...
> 
> Mike,
> 
> Quick questions about SMB_COM_COPY.  I may have asked these before, but 
> I've been running in overload mode lately...
> 
> 1) Is there code to test it still in the distribution.  Some folks here 
>    are interested in playing with it.  I'd also like to see if there are 
>    any implementations that do support it.
> 
> 2) What error is returned (if any)?  Is it consistent?
> 
> Thanks!
> 
> Chris -)-----
> 
> -- 
> Samba Team -- http://www.samba.org/     -)-----   Christopher R. Hertel
> jCIFS Team -- http://jcifs.samba.org/   -)-----   ubiqx development, uninq.
> ubiqx Team -- http://www.ubiqx.org/     -)-----   crh at ubiqx.mn.org
> OnLineBook -- http://ubiqx.org/cifs/    -)-----   crh at ubiqx.org