[jcifs] LastModified in SMB_COM_CLOSE Does Not Work with NT

[andy chernow]

I should of said from the start that I only tested
this with a Samba_2.2.5 Server running on RedHat7.3
kernel_2.4.18-5.  My current application will never
talk to an NT server, that's a relief.

/sLaKr

--- "Michael B. Allen" <miallen at eskimo.com> wrote:
> On Wed, 21 Aug 2002 13:45:08 -0400
> "Andrew Chernow" <achernow at unitedstoragetech.com>
> wrote:
> 
> > Michael,
> >     I saw the message you posted about the lasted
> release of the jCIFS
> > package.
> > 
> > >Didn't get a chance to do NamedPipes available()
> and it doesn't look
> > >like setting last modified through SMB_COM_CLOSE
> works.
> > 
> > I wanted to let you know that I did get
> lastModified time working through
> > SMB_COM_CLOSE.  I just ...
> 
> After examining this more closely it appears that
> this works with Win98 and
> Samba  but  Windows  NT  sp4 does not support
> setting the LastModified time
> through  SMB_COM_CLOSE.  It  is  simply  ignored. 
> The current time is used
> regardless.  When  copying files it is necessary to
> use additional commands
> to set the various attibutes. This helps explain
> performance issues and the
> packet  storm  that  ensues  when copying
> directories with many small files
> to/from  NT  (so  if  you zipped it up you could
> transfer it more safely in
> half the time). 
> 
> Note,  Ethereal  decodes  that time field
> incorrectly. It really is seconds
> from 1970 like the "spec" reads.
> 
> -- 
> A  program should be written to model the concepts
> of the task it
> performs rather than the physical world or a process
> because this
> maximizes  the  potential  for it to be applied to
> tasks that are
> conceptually  similar and more importantly to tasks
> that have not
> yet been conceived. 


__________________________________________________
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
http://finance.yahoo.com