On Wed, 11 May 2005, Nikolaus Rath wrote: > I'm using Gnus 5.10.7. Please tell me what you consider major, you probably > don't want it completely ;-)
Does your Gnus use LIST ACTIVE or GROUP on leafnode? Can you run debug logging (see below), ngrep, ethereal to find that out? If it uses LIST ACTIVE, does it use a wildmat pattern or just a plain group name? I only have a No Gnus here which may not be relevant for what 5.10.7 does. > > In the long term, no touch_newsgroup hacks should be needed to keep > > leafnode subscribed to lowest-traffic groups that see a post or two > > a month. > > Maybe that was the problem. I can't guarantee that there were no more > than 31 days between the postings.. Shouldn't matter. My No Gnus issues "GROUP" commands - and these keep a group that leafnode is subscribed to interesting by refreshing the subscription (bumps up ctime). Same for "LIST ACTIVE" commands that do not contain wildmat patterns, these also keep a subscription fresh. Leafnode considers a group name a pattern if it contains ?, * or [. I tested both in a telnet session, they work as expected and documented. I cannot quite understand that Gnus would allow leafnode to "lose" subscriptions, the only chance for failure would be if Gnus used "LIST ACTIVE *" or just "LIST ACTIVE" and then filtered the group list itself. To verify this, please add debugmode=1 to your leafnode configuration and, if needed, add a line that catches debug logging to your /etc/syslog.conf and reload syslogd (SIGHUP). You should then see debug lines containing "markinterest: ... touched", it works on my machine with leafnode 1.11.2. If you can retrieve lines like "unsubscribing from ... (current time: ...): ctime age ..., mtime age ..." from your past news syslog (they are logged at "INFO" severity) and they are from a 1.10.8 or newer fetchnews, please send a few of them to me. Thanks. -- Matthias Andree -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
