At 03:44 AM 12/19/01 +0100, you wrote:
> > > > groups_at 30 *
> > > > updates at 30 minutes past every hour, and,
> > > I have set this in dnews.conf now, and i know there are new NGs on my
> > > feeder, but they don't show up when i check for new groups.
> > > I will try
> > > groups_at 0 0
> > > now so that it hopefully will update the groupslist every day at
>midnight,
> > > i don't know why i think that this will work while the other setting
>doesn't
> > > but i'll just give it a whirl.
> > A few of things to check...
> > - Are these new groups permitted on your server (according to your ME feed
> > in newsfeeds.conf)?
>
>Yes, my ME feed reads:
>
>site me
> groups *
>
> > - Does the user you login to your server as have permission to read these
> > groups (access.conf)?
>
>Yes, all users have the same permissions:
>
>*:logoff:::*
>192.168.*.*:read,post,:$lookup$:$lookup$:*:
>127.0.0.1:read,post,:$lookup$:$lookup$:*:
>*.*.*.*:read,post:$lookup$:$lookup$:*:
>*:read,post:,groups=private::private.*:add
>
> > - Does your nntp_feeder entry in dnews.conf include these groups in the
>suck
> > list?
>
>Yes, it does. In fact, i know there are these new groups because i saw them
>in the newsreader i use to see if i haven't enforced the smaprules too
>strict. That newsreader warns me if there are new groups.
>
> > - You are sucking from a single feed?
>
>No, i have 3 feeds. the second is a mirror of the first in case the first
>one for some reason fails (it happens sometimes), the third is a low-volume
>free NNTP server.
>I should expect to see somewhere around 50,000 groups, instead there are
>only 32,000-something.
>
> > These could explain dnews knowing about the groups but not sucking them or
> > displaying them to you?
>
>Well, it's not updating the groupslist really. i already added
>
>max_groups 100000
>
>in case the default number were to bit too low.
>
> > If you have multiple feeds, you need to use -
> >
> groups_at2 0 0
> groups_at3 0 0
> > etc.
>
>Have that. Didn't seem to help.
>
> > If that is not the problem, try the following -
> >
> > tellnews cached problem.group.name 2
> > tellnews update (or wait until the next update)
> > (wait until the update completes - 'tellnews status' will say nothing is
> > being sucked)
> > tellnews showgroup problem.group.name
>
>That just updates a newsgoup, it's the list of goups that's the problem.
>The groups that are currently in the list update just fine.
Ok try this in dnews.conf, replace 12 with the next hour in your day :-)
groups_at1 5 12
groups_at2 10 12
groups_at3 15 12
tellnews reload
And then see if it does it, search dnews.log for
find "Processing next background command" dnews.log
to find when it does them.
ChrisP.
