Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!ginosko!uunet!auspex!guy
From: guy@auspex.auspex.com (Guy Harris)
Newsgroups: comp.unix.wizards
Subject: Re: sockets
Message-ID: <2391@auspex.auspex.com>
Date: 28 Aug 89 19:50:33 GMT
References: <20713@adm.BRL.MIL>
Reply-To: guy@auspex.auspex.com (Guy Harris)
Organization: Auspex Systems, Santa Clara
Lines: 15

>Of course, this problem may well just be relevant to SunOS 3.x.  There is
>an option (SO_BROADCAST) that can be set with `setsockoption' in 4.x that
>probably does this correctly---again, I haven't tried this on 4.x yet.

No, it does not, but it is not intended to.  SO_BROADCAST is a
4.3BSD-ism (unless it was in 4.2BSD as well, in which case I'd expect it
to be in SunOS [123].x) and, as noted in the SunOS 4.x and 4.3-tahoe
(and probably 4.3BSD) GETSOCKOPT(2) manual pages:

     The option SO_BROADCAST requests permission to  send  broad-
     cast  datagrams  on  the socket.  Broadcast was a privileged
     operation in earlier versions of the system.

All it does is request permission to send broadcast datagrams; it does
not set the socket up to always transmit them.