This is a discussion on Large binary newreader help please! within the Linux Networking forums, part of the Linux Forums category; ["Followup-To:" header set to alt.os.linux.] On Mon, 03 May 2004 05:07:25 GMT, Ohmster &...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
["Followup-To:" header set to alt.os.linux.]
On Mon, 03 May 2004 05:07:25 GMT, Ohmster <bigbigkitty@invalid.anywhere.com> appears to have said: > ...installed so it might be time to pull up the sleeves, rpm -e slrn away, > download slrn-0.9.7.4.tar.gz (If I can find it.), apply the patch, and > compile. I like it. Rarely use anything else. But then, I'm a loyal slrn fan. Just one thing... 0.9.7.4 you say? 0.9.8.0 has been out for a while now: <http://slrn.sourceforge.net/> If you do get it, and use the jwk patch, be sure to read README.multipart. There's a macro in there that you'll need for proper threading. > BNR2 did not choke on the 2.5M headers. It launched 8 connections, 7 of them > died idle during the header pull and this took a long time, over 2 hours. > Once the headers came down and I refreshed the window, everything was right > there. As Emeril would say, "Bam!". If you're going to get such a high volume of headers on a regular basis, you may be better off with BNR2, if it's as quick as all that. Last time I tried to get over 100,000 headers from a bin group in slrn, it took so long to thread them, that... well, that's when I went and found nget. Then again, I'm running an oldie... 400MHz K6-2. YMMV. > Thanks for the very helpful advice, Johnathan. No problem... have fun! Jonathan -- Don't just hit reply. Email address is broken. Thank your friendly neighborhood spammer. Email replies to: user: jnthn1 domain: earthlink<dot>net |