Hi,
See comments -
[EMAIL PROTECTED] wrote:
Hi, Thanks for past replies. I have another one for you: we have a sucking feed working nicely. But I would like to change DNEWS' default configuration to accomplish the following:
a) the admin selects the groups to be sucked (not the users)
I'm not aware of any way to disable the automatic caching of groups completely. I can't really see any reason to implement such a feature as it would only lead to users wondering why groups weren't updating, and greater support issues for administrators (and us :).
A better alternative would be to restrict the groups available on the server to only they ones you want users to be able to access. You can then set them all as cached, or allow users to cache them when accessed.
In particular the following commands may be handy...
tellnews rmgroup group.name tellnews undelete group.name
b) only the hundred or so groups selected by the admin are sent to NNTP clients in response to LIST command
I should have read ahead, since that is exactly what I proposed above. If you delete the groups they won't be shown to clients. If you wish to keep the groups, but hide them from users, you can modify the access.conf rules to allow this, but you will need to use wildcards to specify group names to avoid complicated access rules.
This may or may not have been easier to do at install time, but I have a few weeks of spool I would like to retain. So I need to transition to the new configuration (if supported) from the current setup (50,000 groups in active file, users in charge of selection).
No problem, easy enough to change now :)
- Roydon L.
Thanks- Gordy DNEWS 5.7b1
