> > No need to restart any daemons or reboot for the changes to take effect.
>>
> You do not have to restart inetd, but you have to force it
> to reread the hosts.allow and hosts.deny files. Send it
> a hangup signal.
No, you don't need to send inetd a HUP signal either - unless it has TCP
wrapp
> iTOOL wrote:
> >
> > If I make changes to the hosts.allow and hosts.deny files, do I have to
> > rebbot for these changes to take effect or is there a service (such as
> > INETD) that I need to kill and re-start?
> Myles Vredenburg answered:
>
> No need to restart any daemons or reboot for the
iTOOL wrote:
>
> If I make changes to the hosts.allow and hosts.deny files, do I have to
> rebbot for these changes to take effect or is there a service (such as
> INETD) that I need to kill and re-start?
>
> thanx
>
> Joseph E. Sheble
> a.k.a. Wizaerd
> Wizaerd's Realm
> http://www.wizaerd.com
On Mon, 28 Feb 2000, you wrote:
> On Mon, 28 Feb 2000, you wrote:
> > If I make changes to the hosts.allow and hosts.deny files, do I have to
> > rebbot for these changes to take effect or is there a service (such as
> > INETD) that I need to kill and re-start?
> >
> cd /etc/sysconfig/
> network
On Mon, 28 Feb 2000, you wrote:
> If I make changes to the hosts.allow and hosts.deny files, do I have to
> rebbot for these changes to take effect or is there a service (such as
> INETD) that I need to kill and re-start?
>
cd /etc/sysconfig/
network restart
John
iTOOL wrote:
>
> If I make changes to the hosts.allow and hosts.deny files, do I have to
> rebbot for these changes to take effect or is there a service (such as
> INETD) that I need to kill and re-start?
Yes, you have to restart or hangup inetd. Like this:
prompt # killall -HUP inetd
That ma
If I make changes to the hosts.allow and hosts.deny files, do I have to
rebbot for these changes to take effect or is there a service (such as
INETD) that I need to kill and re-start?
thanx
Joseph E. Sheble
a.k.a. Wizaerd
Wizaerd's Realm
http://www.wizaerd.com
Featuring 3D, Canvas, and ColdFusio