Date: Thu, 15 Jul 1999 01:13:01 -0400 From: bill@twwells.com (T. William Wells) To: freebsd-questions@freebsd.org Subject: Re: 3.2 hosts.allow Problems Message-ID: <7mjqjo$1fer$1@twwells.com> References: <378CFDFC.16B891CC@cswnet.com> <Pine.BSF.4.05.9907141509360.29705-100000@dt054n86.san.rr.com> <7mj7en$k45$1@twwells.com> <19990715070421.A5157@alaska.cert.siemens.de>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <19990715070421.A5157@alaska.cert.siemens.de>, Udo Schweigert <ust@cert.siemens.de> wrote: : On Wed, Jul 14, 1999 at 07:48:01PM -0400, T. William Wells wrote: : > In article <Pine.BSF.4.05.9907141509360.29705-100000@dt054n86.san.rr.com>, : > Doug <Doug@gorean.org> wrote: : > : > Now nothing is being denied. To restart inetd, I am using "killall : > : > inetd;inetd". : > : : > : First, you shouldn't have to start inetd for changes in : > : hosts.allow to take effect. : > : > "Shouldn't" is correct. Unfortunately, reality doesn't conform. In : > my experience, you have to kill (SIGTERM) inetd and restart it in : > order for hosts.allow changes to take effect. : > : : No, that's not true. I never restarted inetd to enable changes in hosts.allow. : (Only changes in inetd.conf have to be signald via kill -HUP, but that's a : different thing). Well, I'm glad it worked for you. It *did not* work for me. I had a system in which I modified hosts.allow to allow outside access, found myself locked out, and was only able to get back in after restarting inetd. *Without* changing my hosts.allow. So perhaps there's a version difference or something. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7mjqjo$1fer$1>