Up till now we have had to reboot the machine. This fixes the problem
nicely. You also need to restart inetd at some stage.
You use le0 or hme0 - see /etc/hostname.* to find out which interface is
specific to your machine.
On Tue, 12 Aug 1997, Chris Medaglia wrote:
> Hi Sue,
> I haven't heard of this problem specifically, but you might be able to
> save yourself a reboot if you bounce the interface. I've seen problems
> where a previous session will hold onto the socket in TIME_WAIT and not
> let go, then the deamon cannot reuse the socket. Try this:
>
> ifconfig le0 down
> ifconfig le0 up
>
> Use whatever your interface name is instead of le0, and make sure you
> are at the console.
>
> Good luck,
>
> Chris Medaglia
> Putnam Investments
> Andover, MA USA
> 508-974-8326
> ----------------------------------------------
> Sue Gray wrote:
> >
> > Hi SM's
> >
> > We have had a reoccuring problem on our 690 running Solaris 2.5.1
> >
> > Occasionally inetd dies, stopping all services. When it is restarted,
> > telnet still doesnt work - the port appears to be tied up by something.
> > The only solution we have been able to find is to reboot which is not good
> > when we have multiple users trying to do work on the machine.
> >
> > I remember this happening a couple of years ago on the same machine - only
> > the telnet port got tied up without inetd dying. I wonder if it is
> > related.
> >
> > Anyone have any ideas or heard of this happening?
> >
> > Sue
> > ------------ ------------
> > Sue.Gray@Unisa.Edu.Au Infrastructure Team
> > Phone: +61-8-8302-3529 Fax: +61-8-8302 3577
> > Information Technology Unit, University of SA, The Levels, SA 5095, Australia
>
------------ ------------
Sue.Gray@Unisa.Edu.Au Infrastructure Team
Phone: +61-8-8302-3529 Fax: +61-8-8302 3577
Information Technology Unit, University of SA, The Levels, SA 5095, Australia