Date: Sat, 13 Dec 1997 02:08:27 -0600 (CST) From: Kevin Day <toasty@home.dragondata.com> To: jkh@time.cdrom.com (Jordan K. Hubbard) Cc: freebsd-current@FreeBSD.ORG Subject: No more 'nfsd send error 55's! Yaaa! Message-ID: <199712130808.CAA20468@home.dragondata.com> In-Reply-To: <24253.881808973@time.cdrom.com> from "Jordan K. Hubbard" at "Dec 10, 97 06:56:13 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
I grabbed the full sources today, and rebuilt... I can't make the 'nfsd send error 55' happen now... Before, opening elm or pine on a machine that had to load the /var/mail file via nfs would take 10+ minutes, and fill the console with 'nfsd send error 55'... That's gone now.. So, whoever fixed it, thanks... I'm not sure what fixed it, or when the fix was put in, since I don't see any nfs checkins recently, but I'm not going to argue. :) However, there's a new error randomly coming up: sendmail[19390]: NOQUEUE: SYSERR: putoutmsg (31.net10.nauticom.net): error on output channel sending "220 home.dragondata.com ESMTP Sendmail 8.8.5/8.8.5; Sat 13 Dec 1997 01:33:59 -0600 (CST)": Broken pipe sendmail[19390]: NOQUEUE: SYSERR: putoutmsg (31.net10.nauticom.net): error on output channel sending "250 home.dragondata.com Hello test@31.net10.nauticom.net [208.148.242.31], pleased to meet you": Broken pipe /kernel: pid 19390 (sendmail), uid 0: exited on signal 11 It's not major, just an interesting swap. :) Kevin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199712130808.CAA20468>