[jcifs] RE: jcifs digest, Vol 1 #557 - 4 msgs

Mon Dec 2 10:34:05 EST 2002

> -----Original Message-----
> From:	Sujit Jagdev [SMTP:sujit.jagdev at casero.com]
> Sent:	Thursday, November 28, 2002 12:10 PM
> To:	jcifs at lists.samba.org
> Subject:	[jcifs] RE: jcifs digest, Vol 1 #557 - 4 msgs
> 
> It would appear that the old problem of jcifs corrupting files when one
> tries to move them from a directory on a particular share to another has
> appeared again. I have tried to use the SmbFileInputStream and
> SmbFileOutputStream Classes as well as the copyTo function in the
> SmbFile class
> 
	So you used SmbFileInputStream and SmbFileOutputStream to serially
	copy each file one after the other? You do realize that you cannot use
	multiple threads acting on the same SmbFile instance right? Just like you
	would not with java.io.File.

> , but this menacing corruption keeps coming back.
> The worst thing is that it is not easily replicated. I must have moved
> over ten thousand files since I thought it was fixed.
> Oh! One more thing I was attempting to move .mp3/.jpeg files.
> 
	Please send me a sample of a good mp3/jpeg and a "corrupted" one.
	Perhaps I can gleen some information from their binary edit distances.

> Sujit
> 
> -----Original Message-----
> From: jcifs-request at lists.samba.org
> [mailto:jcifs-request at lists.samba.org] 
> Sent: Thursday, November 28, 2002 12:00 PM
> To: jcifs at lists.samba.org
> Subject: jcifs digest, Vol 1 #557 - 4 msgs
> 
> Send jcifs mailing list submissions to
> 	jcifs at lists.samba.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.samba.org/listinfo/jcifs
> or, via email, send a message with subject or body 'help' to
> 	jcifs-request at lists.samba.org
> 
> You can reach the person managing the list at
> 	jcifs-admin at lists.samba.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of jcifs digest..."
> 
> 
> Today's Topics:
> 
>    1. CVS update: jCIFS/trees (crh at samba.org)
>    2. CVS update: jCIFS/junk (crh at samba.org)
>    3. CVS update: jCIFS (crh at samba.org)
>    4. Re: CVS update: jCIFS/junk (Christopher R. Hertel)
> 
> --__--__--
> 
> Message: 1
> To: jCIFS at samba.org
> Date: Thu, 28 Nov 2002 05:05:13 +0000 (GMT)
> From: crh at samba.org
> Subject: [jcifs] CVS update: jCIFS/trees
> 
> 
> Date:	Thu Nov 28 05:05:13 2002
> Author:	crh
> 
> Update of /data/cvs/jCIFS/trees
> In directory dp.samba.org:/tmp/cvs-serv4223/trees
> 
> Removed Files:
> 	AVLTree.java BinaryTree.java 
> Log Message:
> Removing this.  It was a false start.  jCIFS is moving well in a
> different 
> direction.
> 
> 
> Revisions:
> AVLTree.java		1.1 => NONE
> 	
> http://www.samba.org/cgi-bin/cvsweb/jCIFS/trees/AVLTree.java?rev=1.1
> BinaryTree.java		1.1 => NONE
> 	
> http://www.samba.org/cgi-bin/cvsweb/jCIFS/trees/BinaryTree.java?rev=1.1
> 
> --__--__--
> 
> Message: 2
> To: jCIFS at samba.org
> Date: Thu, 28 Nov 2002 05:05:13 +0000 (GMT)
> From: crh at samba.org
> Subject: [jcifs] CVS update: jCIFS/junk
> 
> 
> Date:	Thu Nov 28 05:05:13 2002
> Author:	crh
> 
> Update of /data/cvs/jCIFS/junk
> In directory dp.samba.org:/tmp/cvs-serv4223/junk
> 
> Removed Files:
> 	Dump.java MalformedNetBIOSException.java NetBIOSName.java 
> 	README WINSListner.java 
> Log Message:
> Removing this.  It was a false start.  jCIFS is moving well in a
> different 
> direction.
> 
> 
> Revisions:
> Dump.java		1.1 => NONE
> 	http://www.samba.org/cgi-bin/cvsweb/jCIFS/junk/Dump.java?rev=1.1
> MalformedNetBIOSException.java		1.1 => NONE
> 	
> http://www.samba.org/cgi-bin/cvsweb/jCIFS/junk/MalformedNetBIOSException
> .java?rev=1.1
> NetBIOSName.java		1.1 => NONE
> 	
> http://www.samba.org/cgi-bin/cvsweb/jCIFS/junk/NetBIOSName.java?rev=1.1
> README		1.1 => NONE
> 	http://www.samba.org/cgi-bin/cvsweb/jCIFS/junk/README?rev=1.1
> WINSListner.java		1.1 => NONE
> 	
> http://www.samba.org/cgi-bin/cvsweb/jCIFS/junk/WINSListner.java?rev=1.1
> 
> --__--__--
> 
> Message: 3
> To: jCIFS at samba.org
> Date: Thu, 28 Nov 2002 05:07:09 +0000 (GMT)
> From: crh at samba.org
> Subject: [jcifs] CVS update: jCIFS
> 
> 
> Date:	Thu Nov 28 05:07:09 2002
> Author:	crh
> 
> Update of /data/cvs/jCIFS
> In directory dp.samba.org:/tmp/cvs-serv4417
> 
> Added Files:
> 	README 
> Log Message:
> Redirect people to the correct site.
> 
> 
> Revisions:
> README		NONE => 1.1
> 	http://www.samba.org/cgi-bin/cvsweb/jCIFS/README?rev=1.1
> 
> --__--__--
> 
> Message: 4
> Date: Wed, 27 Nov 2002 23:17:34 -0600
> From: "Christopher R. Hertel" <crh at ubiqx.mn.org>
> To: jcifs at samba.org
> Subject: Re: [jcifs] CVS update: jCIFS/junk
> 
> Hmmm... fascinating...
> 
> There was an old CVS repository for the jCIFS code on the Samba.Org
> site.
> I used it when I started the project, but as things evolved we stopped 
> using it.  (I don't remember exactly why, but it is a bit of a shame, 
> really.)
> 
> Anyway, the code was old and unused so I was clearing it out.  I didn't
> realize that the update notices went to the whole list.
> 
> Pardon the noise.  It's just me cleaning house.
> 
> 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
> 
> 
> --__--__--
> 
> _______________________________________________
> jcifs mailing list
> jcifs at lists.samba.org
> http://lists.samba.org/listinfo/jcifs
> 
> 
> End of jcifs Digest
> 
> 
> -----
> 
> The information contained in this message is proprietary of Casero Inc.,
> protected from disclosure, and may be privileged. The information is
> intended to be conveyed only to the designated recipient(s) of the
> message. If the reader of this message is not the intended recipient,
> you are hereby notified that any dissemination, use, distribution or
> copying of this communication is strictly prohibited and may be
> unlawful. If you have received this communication in error, please
> notify us immediately by replying to the message and deleting it from
> your computer. Thank you.
>