Hi, ... You don't have to. the tcp wrapper is started with every connection attempt, re-reading /etc/hosts.[allow|deny]. Even programs "directly" linked against libwrap (such as syslogd or sshd) don't have to be restarted; libwrap reads it's configuration files on each new connection.
Is syslogd really linked against libwrap ? I read this the first time.
Bitzer,Gerd schrieb am Thu, 15 Nov 2001 um 12:17:
Even programs "directly" linked against libwrap (such as syslogd or sshd)
Is syslogd really linked against libwrap ? I read this the first time.
Whoops. You're right, syslogd (at least the way SuSE release[s|d] it) is not linked against libwrap. Anyway, I seem to remember a couple of projects trying to implement this for what they believed to be increased security. libwrapping syslogd in fact would arise a couple of problems. Anyway, this was not the issue here - so s/syslogd/sendmail/ (yes, sendmail _is_ linked against libwrap since SuSE 7.1. Lost a couple of mails because of that :-/ ) or s/syslogd/portmap/ or whatever. Regards, Bastian -- Bastian Friedrich bastian@bastian-friedrich.de Adress & Fon available on my HP http://www.bastian-friedrich.de/ \~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\ \ You can't go home again, unless you set $HOME.
participants (2)
-
Bastian Friedrich
-
Bitzer,Gerd