Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mira.net.au!inquo!news.uoregon.edu!news.bc.net!news.mindlink.net!uniserve!usenet From: tom@uniserve.com (Tom Samplonius) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: nntp_access resetting question Date: 17 Jan 1996 17:47:42 GMT Organization: UNIServe Online Lines: 35 Distribution: world Message-ID: <4djcnu$li0@atlas.uniserve.com> References: <4cq4eu$flf@gol2.gol.com> <4d3a4s$mtt@mgulvt.mgul.ac.ru> NNTP-Posting-Host: tapehost.uniserve.com Mime-Version: 1.0 Content-Type: Text/Plain; charset=US-ASCII X-Newsreader: WinVN 0.99.6 In article <4d3a4s$mtt@mgulvt.mgul.ac.ru>, and@mgulvt.mgul.ac.ru says... > >Doug Lerner (doug@gol.com) wrote: >: When I change DNS data files, I must > >: kill -HUP <process-ID> > >: in order for the changes to take effect. > >: When I change the nntp_access file (permissions for different IP >: addresses to read/write/post news) do I need to do something similar to >: cause the changes to take effect? > >: I just tried adding some IP addresses for Portmaster IP addresses, but >: was unable to read news from those addresses. > >Hi! > >I use INN1.4 and when I change my file nntp.access, I get results without >the reloading anything. May be your news system use another file for users >permissions? You are both wrong. INN 1.4 stores news server access information in hosts.nntp. You can tell INN to reload hosts.nntp with "ctlinnd reload hosts.nntp x". For any connects that do not match anything in hosts.nntp, INN starts a nnrpd proccess. INN 1.4 stores news reader access information in nnrp.access. This file is loaded by each nnrpd process on startup, so there is no need to reload anything. Tom