1CONTROLCHAN(8) System Manager's Manual CONTROLCHAN(8)
2
3
4
6 controlchan - channel-fed control message handler
7
9 controlchan
10
12 Controlchan removes the responsibility for handling control messages
13 (except cancels) from innd(8) and instead processes them from a channel
14 or file feed. To reduce load, controlchan keeps a copy of control.ctl
15 in memory and checks permissions (including any required PGP headers)
16 before any scripts are called. Also, the default (``bad message'')
17 case is handled internally. The ``drop'' case is handled with far less
18 fuss.
19
20 Normally, controlchan is invoked by innd(8) as configured in newsfeeds.
21 An example entry is below. Make sure that you've created the newsgroup
22 control.cancel so that controlchan doesn't have to scan through can‐
23 cels, which it won't process anyway.
24
25 controlchan!\
26 :!*,control,control.*,!control.cancel\
27 :Tc,Wnsm\
28 :<pathbin in inn.conf>/controlchan
29
30 Note that in the (very, very unlikely) event that you need to process
31 ihave/sendme control messages, be sure that logipaddr is set to false
32 in inn.conf, because in this case controlchan needs a site name, not an
33 IP address.
34
35 Controlchan tries to report all log messages through syslog(3), unless
36 connected to an interactive terminal. To enable syslog(3)'ing for ver‐
37 sions of Perl prior to 5.6.0, you will need to have run ``h2ph'' on
38 your system include files at some point (this is required to make
39 ``Sys::Syslog'' work). If you have not done so, do this:
40
41 cd /usr/include
42 h2ph * sys/*
43
44 If you run FreeBSD, you will need to run the following in addition:
45
46 h2ph machine/*
47
49 Written by Katsuhiro Kondou <kondou@nec.co.jp> for InterNetNews. This
50 is revision 5909, dated 2002-12-03.
51
53 control.ctl(5), inn.conf(5).
54
55
56
57 CONTROLCHAN(8)