I've seen this behavior in the past. My impression is that it is load related.
If you do a grep on ETIMEDOUT in /usr/src/sys/netinet, you will see where
the tcp stack may return this message. There may be some sysctl params relating
to timers that you can muck with.
Rick
Graham Barr wrote:
> On Thu, Jun 07, 2001 at 10:33:50AM -0700, Matt Dillon wrote:
> >
> > :
> > :Thanks, I will try setting errno, but I don't think it is signals.
> > :I have been running truss on the process. The relevant part is
> > :
> > :gettimeofday(0xbfbffa54,0x0) = 0 (0x0)
> > :select(0x50,0x93f8c90,0x0,0x0,0xbfbffa74) = 3 (0x3)
> > :read(0x16,0xa2da000,0x8000) ERR#60 'Operation timed out'
> > :
> > :In fact there are no signals in the whole truss output
> > :
> > :Graham.
> >
> > What type of descriptor is the read being performed on? A TCP
> > connection or, say, a reading a file over NFS?
>
> It is a TCP/IP connection.
>
> Graham.
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
