Keith,
Do you have hostmon setup to use a different port than normal? Also
check your /tmp for the run file and make sure that the reference to
the open file descriptor for any instance of hostmon is gone.
Other than occaisional dying, I have a slew of Solaris boxes with 2.6
on them run hostmon just fine. Korn shell script to properly eradicate
and restart dead ones available. If you change the default port for
noclogd, make sure you are very thorough in the source and hostmon
knows about it.
--Rick
On Tue, Feb 02, 1999 at 02:44:25PM -0500, Jonathan A. Zdziarski wrote:
> I get that wherever I improperly set AF_INET and/or SOCK_STREAM. I
> haven't got the time but you might want to check the code to see if
> this was numerically defined somewhere. Solaris has a different value
> for a tcp stream connection.
>
> Tue, 2 Feb 1999, Keith Libitz
> wrote:
>
> > My apologies if this has already been hashed out.
> > I read through the archives and worked out my other
> > issues but I can't seem to clear this final hurdle.
> >
> > When I run the hostmon-client on my Solaris 2.6 machine
> > everything goes fine until it attempts to set up the
> > telnet daemon when I get the following:
> >
> > $ ./hostmon-client
> > OSTYPE : SunOS 5.6 sun4u
> > Loading File : hostmon-client.solaris2
> > 27574
> > $ socket() call failed: Protocol not supported
> >
> > What am I missing?
> > Any help is greatly appreciated!
> >
> > Regards,
> > Keith
> >
>
> Thank you,
>
> Jonathan A. Zdziarski
> Sr. Systems Administrator
> Netrail, inc.
> 888.NET.RAIL x240
--
^^^^^^^^^^^^^^
Rick Robino mailto:rrobino@gstis.net
Manager, Internet Operations, GST/Whole Earth http://www.gstis.net
Portland: v. (503) 416-1517 f. (503) 416-1555 p. (503) 703-0728
|