setsockopt(2) behaviour in BSD sockets.

[Chris Torek]

In article <758 at cernvax.UUCP> lekkas at cernvax.UUCP (George P. Lekkas) writes:
-... a setsockopt at the TCP protocol level, that is set the level=6.
-This call was made on the socket returned from accepting a connection
-request, at the server side.  All sockets were of the SOCK_STREAM type ....
-Just add the setsockopt(msgsock,..) call after the msgsock = accept()
-line. Optval and optlen were set to zero, optname can be 0 or SO_DEBUG.
-... the result: ... to crash ("protection trap 9" or something)
-	Should this be so easy?

Certainly not.  And indeed, my machine (an 8250 running 4.3BSD-tahoe,
more or less) does not crash.  I get an `EINVAL' (invalid argument)
error.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris at mimsy.umd.edu	Path:	uunet!mimsy!chris