standalone-nnrpd "dies" when hitting ressource limits

Russ Allbery rra at stanford.edu
Thu Nov 16 07:20:01 UTC 2000


Anonymous Coward <newsb'stard at FREE-N0RP.NetScum.dK> writes:

> There's another problem I've noted with nnrpd -D ...  If you make
> changes to the inn.conf file that affect nnrpd, the newly forked nnrpds
> don't catch these changes, and, for example, the long-running nnrpd -D
> is still trying to send to a long-dead nnrpdpostinghost, while those
> nnrpds spawned from tcpswerver have caught the change...

> Normally not a big deal, but for sites that do make a change affecting
> nnrpd, they need to remember that the master nnrpd daemon needs to learn
> about the change

Thanks, added a note about this to the man page.

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



More information about the inn-workers mailing list