Re: Problems with shutdown of crserver for non-tcpip connections

[email protected] said:
> Dumb question: Can you run one of the back end crservers in gdb, and
> have it follow the parent or break on fork()?  That would give you a
> hint as to what's going on.

> -Sean 

I've finally gotten around to implementing Sean's suggestion, and I've found 
that the process causing all the problems is created by clone() rather than 
fork() or its variants.  It's being created in elan3_attach(), which is a call 
used in management of the Quadrics device.  Apparently the Quadrics folks have 
added a watcher process of some sort in their most recent software release and 
that process is surviving the teardown process for the crserver.  My 
apologies; this problem shouldn't be common to other networks like GM.  I'll 
figure out what is supposed to make that process die and see if I can get the 
crserver teardown to do it.

-Joel
 [email protected]



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click