nnrpd: NNRPACCESS reading weirdness, and fix
cm at tahina.priv.at
Mon Sep 18 22:15:06 UTC 2000
nnrpd allocates a global variable NNRPACCESS for the name of the
"readers.conf" file, and copies the respective value from inn.conf
into that variable (in main()).
in perm.c, PERMgetaccess(), which actually reads readers.conf, takes
the name from the inn.conf variables directly again, making the
copying in main() redundant.
the attached diff
a) passes NNRPACCESS to PERMgetaccess(), which seems the logical
thing to do
b) adds a "-c conffilename" command line flag to nnrpd, whichs
provides a filename to use instead of "readers.conf" (or whatever
this allows me to run multiple instances of nnrpd on different IP
addresses with completely different access files. the reason for this
comes from my setup: I run a open-access read-only archive of a
single newsgroup on my server, and I offer full access to some
friends, authenticated via passwords.
the netscape "newsreader" component, now, on connecting to the
server, sees "no posting" because initially only one group is visible
read-only; when netscape authenticates, all groups become visible,
and posting is possible, but the "new post" button (and respective
menu entry) don't get activated, so you can only post follow-ups.
so the solution was to switch the archive part to another IP address,
and I was searching for a solution to provide that nnrpd to another
access file; the workaround I used until now was to call it with an
INNCONF environment variable pointing to a second inn.conf which in
turn contained a pointer to the second readers.conf (BTW: this
parameter doesn't seem to be mentioned in the 2.3 manpages anymore).
christian mock in vienna, austria -- http://www.tahina.priv.at/~cm/
VIBE!AT http://www.vibe.at/ ** wir sind nicht zum spass hier.
-- Attached file included as plaintext by Listar --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.2 (GNU/Linux)
Comment: Exmh version 2.1.1 10/15/1999 (debian)
-----END PGP SIGNATURE-----
More information about the inn-bugs