Return to BSD News archive
#! rnews 1613 bsd Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nntp.coast.net!news.sprintlink.net!helena.MT.net!nate From: nate@trout.sri.MT.net (Nate Williams) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: trn and unexpected close of socket? Date: 1 Jan 1996 17:50:40 GMT Organization: SRI Intl. - Montana Operations Lines: 29 Message-ID: <4c96tg$nq7@helena.MT.net> References: <4c69cc$81o@news.cerf.net> Reply-To: "Nate Williams" <nate@sneezy.sri.com> NNTP-Posting-Host: trout.sri.mt.net In article <4c69cc$81o@news.cerf.net>, Elya Kurktchi <elya@nic.cerf.net> wrote: >Anybody know why trn would bomb out with the message: > >Unexpected close of server socket That happens when your news server closes the socket w/out telling the client ahead of time. My NNTP host does this everyday at 5 in the afternoon, so I have to re-connect. >When I launch trn, it connects to my >news server (winNT), I see a listing, and when I type = to see a listing >or return to read, it quits trn with the message above. I'm using >FreeBSD v2.0.5. It sounds like a problem with the news Server expecting something that trn is not provided. This is common on Usenet software running on M$ products which are PC-centric, and don't do things the 'standard' way. Look at the logs on the news server and see if you can debug the problem. Nate -- nate@sneezy.sri.com | Research Engineer, SRI Intl. - Montana Operations nate@trout.sri.MT.net | Loving life in God's country, the great state of work #: (406) 449-7662 | Montana. home #: (406) 443-7063 | A fly pole and a 4x4 Chevy truck = Heaven on Earth