control.ctl

[Russ Allbery]

Forrest Aldrich <forrie at forrie.com> writes:

> So, am I to interpret this as I'll need to edit the control.ctl file for
> every heirchy I wish to carry, then optionally delete or comment it out
> if I decide to remove a group later?

> That can't be right.

You need to reduce control.ctl to only listings for the *hierarchies* that
you carry and for which you want to honor control messages.  You don't
have to list individual groups, unless your control message policy is that
specific.

> We've set up a server with just a handful of groups to be fed, and we
> have some private groups established that will not be propogated.  I'd
> like for only the groups we decide to carry, as outlined in the active
> file, to be fed any control messages.

I don't know what you mean by "fed any control messages."

If you want those groups to be automatically created or deleted based on
control messages, you have to add appropriate entries to control.ctl.  If
you're only taking selected groups in a hierarchy, the patterns in the
default file are probably too general for you.

Alternately, you can simply maintain your active file by hand, watching
the relevant groups for changes in the hierarchies that you carry and
implementing them with ctlinnd.  This is what most people with very
limited feeds do.

-- 
Russ Allbery (rra at stanford.edu)             <http://www.eyrie.org/~eagle/>