[jcifs] threading

[Christopher R. Hertel]

On Sat, Feb 22, 2003 at 05:42:24AM -0500, Michael B. Allen wrote:
> 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.

What, me possibly being right about something?  ;)

> 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.

Again, I would want to know what is actually happening on the wire.  My 
*hope* is that we could see which exchange is actually blocking.

> > 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.
> 
> Mike
> 
> -- 
> 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. 

-- 
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