Hosts.allow and netatalk/cups

Bob Hall rjhjr at cox.net
Tue Jan 11 08:30:53 PST 2005


On Tue, Jan 11, 2005 at 02:37:23PM +0700, Olivier Nicole wrote:
> To my knowledge, the effects in /etc/hosts.allow are immediate as soon
> as you save the modified file.
> 
> And I have been using it that way for many years.
> 
> No need to killall -HUP inetd, no need to reboot.
> 
> If after a change the service is still not available:
> 
> - you did not allow the right thing
> 
> - the servcie would not be working even without tcp wrapper
> 
> Try to add ALL : ALL : allow at the top of /etc/hosts/allow. Does the
> service work? Then you made a mistake when trying to open tcp wrapper
> for that specific service. Else the problem is not with tcp wrapper /
> hosts.allow.

Thanks for the comments, but changes to /etc/hosts.allow don't take
effect until the system is rebooted. And when the system is rebooted,
they definitely take effect.

Two entries that take effect if and only if the system is rebooted:
	smbd : .krig.net : allow
	afpd : .krig.net : allow
Commenting these out and saving the file has no effect. Rebooting the
system stops Windows and Mac file sharing. Uncommenting them and saving
the file has no effect. Rebooting the system restores Windows and Mac
file sharing.

uname -a
FreeBSD kongemord.krig.net 5.2.1-RELEASE FreeBSD 5.2.1-RELEASE #0: Mon Sep 13 00 :17:04 EDT 2004 kongemord.krig.net:/usr/obj/usr/src/sys/KONGEMORD0  i386

Bob Hall


More information about the freebsd-questions mailing list