I already posted this message but I had no answer. Sincerely, I think it is
a bug and I'd like to hear developers on this.
Platform:
- HP-UX 11.00
- HP C/ANSI C Compiler (B.11.01.06)
Copying a (large) directory structure from a NT share, interactive
command:
# smbclient //machine/share password
>prompt
>recurse
>mget *
fails to copy 76th, 115th, 154th file of directories.
Regards
Domenico Viggiani
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
Dear Tobias, I received your answer (and I thank you!) but my problem seems to be different: smbclient fails to copy ONLY 76th, 115th, 154th, ... file of a dir! Other ideas? Suggestions? Domenico Viggiani>I wrote an answer last Tuesday, maybe it didn´t get through... > >I had something similar. The files that could not be copied turned out >to be open files on NT. I don´t know WHY this won´t work but after I >closed them (resp. stopped the services that kept them open) it worked. > > Tobias > > > >Domenico Viggiani wrote: > > Copying a (large) directory structure from a NT share, interactive > > command: > > # smbclient //machine/share password > > >prompt > > >recurse > > >mget * > > fails to copy 76th, 115th, 154th file of directories.______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com
Thank you for your message. I really think we have the same problem. I know that samba team is hiring on the mailing list and it is not a good idea writing them directly. I think that we should prepare a serious test-case and submit it on the list again. Write me if you have other suggestions. Bye from Italy Domenico Viggiani>Ok, I think i have something like you... >More precise , I try to do a tar of a complete NT4 Workstation from an >sgi origin 200 IRIX6.5. >As i am paranoiac for backup , i do them two times and i discover >misfits between the same tar??? >I try the same as you and get more or les the same problem... >Finally, I try the following: > >script lsfile1 >smbclient //machine/share password >recurse >ls >quit >^D > >script lsfile2 >smbclient //machine/share password >recurse >ls >quit >^D > >gdiff lstfile1 lstfile2 > >Of course, the files are different when the directory structure is >large. > > >The common of these test seems that smbclient has some difficulties when >parsing directories in order to >find filenames and attributes. But I don't know the parameters to change >in order to gain true results. > >I think it is an important problem for those who are using extensively >Samba for professionnal use. >Do you think it could be possible to ask the samba team? > >Best regards >D.MARS >______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com
OK. I think I'm starting to figure out how to use smbclient, but
now I've run into a really annoying non-feature.
I'd like to alert some of these folks that have been infected wih
the Qaz virus that they are infected. I thought that this could
be a simple matter, *if* they were opening sharing their C: drives.
I found at least a couple of infected hosts that are indeed sharing
C:, so I used smbclient to attach to one of them.
Now I need to get this guy's e-mail address, so that I can mail him
a message, telling him he's infected with Qaz.
I think that I fugured out where his e-mail address might be stashed
on his disk drive. It looks like he's got Netscape installed, and so
I surmize that his e-mail address is probably stashed in some preferences
file, somewhere in the vicinity of:
C:\Program Files\Netscape\Communicator\
I'd like to go snooping around in that directory, and see if I could
find it, but there's a problem... smbclient doesn't seem to grasp the
fact that nowadays, filenames on Windows can contain spaces. Thus, I
can't even `cd' into the `Program Files' directory! Humph.
Have any of you got a fix for this?