This question has been posed at least twice now, and received no response. I've simply switched to using leafnode - at least on my system, it provides _much_ quicker response (reading the active file, doing the xover upon entering the group, etc.) than nntpcache ever thought about doing. If you have less than 5 users who will use your nntp server, I'd recommend this route. Above 5 or 10, I'd switch over to using inn + suck (got that setup this weekend, but quickly determined it was too much work considering it's just me hitting my server). -Chris -- Chris A. Mattingly camattin@camattin.com http://www.camattin.com/ (Don't waste your time :) ) http://www.freebsdzone.com/ (Please visit and give the requested feedback!) On Thu, 30 Mar 2000 james@wwnet.net wrote: > > I am having a strange problem. > If I start nntpcached without any command line options, everything seems > to be working right except that port 119 doesn't get opened. > If I start nntpcached with -n (or by adding a line to log anything right > before NNTPportFD = createPort (con->bindAddr);) port 119 is opened and > everything runs fine. This is on FreeBSD 3.4-Release > > I was trying to find the archives of the list to see if anyone else has > had the same problem, but of the 3 links I could find none of them seemed > to carry the list anymore. > > James > > >
