SQLNET V2 question

We're still on V1 sqlnet and have an ongoing problem with our PC connections. When a PC based client re-boots their PC during an active connection to the database, that session's daemon usually does not go away on the UNIX side and often seems to run away eating up CPU as fast as possible.
Question: Does anyone out there know how V2 sqlnet handles this type of  lost connection? Received on Tue Jan 09 1996 - 13:35:27 CST