[jcifs] threading

Michael B. Allen miallen at eskimo.com
Sat Feb 22 21:42:24 EST 2003

On Sat, 22 Feb 2003 03:49:42 -0500
Dan Dumont <dan at canofsleep.com> wrote:

> I tried T2Crawler and messed around, broke it, then tried it again.
> I observed some interesting behavior that would seem to indicate that
> Christopher Hertel might have been right on the ball.
> When I tell the threads to start on many hosts that I know to be up, the
> threads go, and the output mixes in my console (desired effect).
> However, when I stick in a host that does I know will not respond....
> instant blocking...

Odd. I've never seen such a thing happen. A host that does not repond
to a SYN packet will block the thread however it should not block all
threads. Not unless you're using non-native thread support.

> It seems that a lookup is in progress and is blocking up the whole mess.
> Is there an easy way that I can disable lookups in the package?
> I really don't need them.  I am using ip addresses as it is to connect
> to smb hosts, so I do not need the added feature of name lookups.

See the jcifs.smb.client.resolveOrder property.


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 important, to tasks that have not
yet been conceived. 

More information about the jcifs mailing list