> > > > To update every two hours, you could use the following setting -
> > > > groups_at 30 0,2,4,6,8,10,12,14,16,18,20,22
> > > > This will update the group lists at 0030,0230...,2230
> > > So:
> > > groups_at 30
> > > will refresh the groups list ever hour at 30 minutes past the hour?
> > Nearly, you need to tell it what hours to do this, as well as the
minutes.
> > 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)?
- Does the user you login to your server as have permission to read these
groups (access.conf)?
- Does your nntp_feeder entry in dnews.conf include these groups in the suck
list?
- You are sucking from a single feed?
These could explain dnews knowing about the groups but not sucking them or
displaying them to you?
If you have multiple feeds, you need to use -
groups_at2 0 0
groups_at3 0 0
etc.
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
You should see a list of articles, if not, please send us
([EMAIL PROTECTED]) your access.conf, dnews.conf, and newsfeeds.conf,
plus your user name on your local server (if applicable), and the name of a
problem group, and we'll see if we can spot the problem.
- Roydon L.
