Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nntp.coast.net!news.kei.com!newsfeed.internetmci.com!uuneo.neosoft.com!conrads From: conrads@dolphin.neosoft.com (Conrad Sabatier) Newsgroups: comp.unix.bsd.freebsd.misc,news.software.readers Subject: Re: mthreads for trn (FreeBSD) Date: 24 Jun 1996 23:27:49 GMT Organization: What? Me, organize? Lines: 52 Message-ID: <4qn89l$kdc@uuneo.neosoft.com> References: <4qfgj2$17s_002@mypc.neosoft.com> <4qmhrf$mv3@helena.MT.net> Reply-To: conrads@neosoft.com (Conrad Sabatier) NNTP-Posting-Host: 206.27.165.132 Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:22049 news.software.readers:28086 In article <4qmhrf$mv3@helena.MT.net>, Nate Williams <nate@sneezy.sri.com> wrote: >[ Emailed to posted as well as posted ] > >In article <4qfgj2$17s_002@mypc.neosoft.com>, >Conrad Sabatier <conrads@neosoft.com> wrote: >>This looks like just the thing to cure my problem with trn and its excessive >>rereading of the remote active file. Only problem is, I'm not good at this >>porting business. I downloaded the mthreads-3.1.tar.gz, tried to install >>it, but I get a compile error. Seems mthreads.c is calling "setpgrp", >>whereas the FreeBSD libraries have replaced this routine with "setpid". > >Umm, what version of FreeBSD are you using. I've got setpgrp() on my >2.1R box. :) OK, I wasn't really too clear on that before. mthreads.c had the following: (void*) setpgrp() (or something like that) This caused the "wrong number of parameters" complaint from the compiler. So I checked the include lib and found a comment to the effect that setpid had supplanted setpgrp, although both routines were still present (setpgrp, BTW, requires two pointer args, if I recall correctly). Anyway, it finally dawned on me: Hey! The returned value from setpgrp is being discarded anyway in mthreads.c (don't ask me why it's even being called in the first place), so I commented it out, the compile went off without any further hitches, and now I've got a working mthreads. >And, I don't think mthreads is going to help you since it's for >threading a news directory which doesn't use the new style threads. TRN >used to use it's own 'propriatary' format, but switched to the standard >format long ago. Yes, I finally realized what mthreads actually does. It's still useful, if your trn was compiled to support it (definitely speeds up opening a group, if the group's thread file is up to date). But it requires you to run mthreads periodically to update the thread database, which is kind of a pain. Would be nice if trn would sense an outdated thread file and update it on the fly. >If you're using NNTP to read your news, *make* sure your remote site >supports Overview support and compile trn to use it. You'll still have >to download the thread files, but you won't have to thread on the fly. I finally compiled the nntpclient1.6 package and it solved everything. Now, trn will use either the local thread file, if it determines that it's up to date, or NOV from the remote otherwise. Best of both worlds! And no more interminable updates every time I post. A 100% cure! Yay! :-) -- Conrad Sabatier -- http://www.neosoft.com/~conrads