Article View: comp.bugs.4bsd
Article #1093Re: setsockopt(2) behaviour in BSD sockets.
From: Chris Torek
Date: Wed, 27 Jul 1988 04:00
Date: Wed, 27 Jul 1988 04:00
15 lines
1188 bytes
1188 bytes
In article <758@cernvax.UUCP> lekkas@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@mimsy.umd.edu Path: uunet!mimsy!chris
Technical Details
Message-ID:
<12687@mimsy.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!lll-winken!lll-tis!ames!umd5!mimsy!chrisReferences:
<758@cernvax.UUCP>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!lll-winken!lll-tis!ames!umd5!mimsy!chris From: chris@mimsy.UUCP (Chris Torek) Newsgroups: comp.bugs.4bsd Subject: Re: setsockopt(2) behaviour in BSD sockets. Message-ID: <12687@mimsy.UUCP> Date: 27 Jul 88 04:00:59 GMT References: <758@cernvax.UUCP> Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742 Lines: 14