Re: Hosts.allow and netatalk/cups
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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hosts.allow and netatalk/cups
On Tue, Jan 11, 2005 at 02:31:47AM -0500, Bob Hall wrote: Three questions: How do I cause changes in the hosts.allow file to take effect without rebooting? Everything I've seen says to restart inetd, but I'm not using inetd. I searched with different keywords and found the answer to this in the archives. Searching the archives, Googling, and experimentation still haven't turned up an answer to the two below. How do I compile netatalk without CUPS? I don't see any obvious switches, but there has to be something that tells Make to use CUPS, because it gives a message saying that it's checking if CUPS can be included. How do I get netatalk to use the dbd cnid scheme? It ignores the path name cnidscheme:dbd setting in AppleVolumes.default and the - -cnidserver localhost:4700 setting in afpd.conf. Regardless of what the cnidscheme setting is, it announces that's there's no cnid scheme selected and uses the default. Bob Hall ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Hosts.allow and netatalk/cups
Three questions: How do I cause changes in the hosts.allow file to take effect without rebooting? Everything I've seen says to restart inetd, but I'm not using inetd. How do I compile netatalk without CUPS? I don't see any obvious switches, but there has to be something that tells Make to use CUPS, because it gives a message saying that it's checking if CUPS can be included. How do I get netatalk to use the dbd cnid scheme? It ignores the path name cnidscheme:dbd setting in AppleVolumes.default and the - -cnidserver localhost:4700 setting in afpd.conf. Regardless of what the cnidscheme setting is, it announces that's there's no cnid scheme selected and uses the default. Bob Hall ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hosts.allow and netatalk/cups
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. Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
