Re: inetd & inetd.conf

2004-06-29 Thread Chris Metzler
On 29 Jun 2004 12:23:22 +0100 Keith O'Connell <[EMAIL PROTECTED]> wrote: > > Hi, > > I just had to edit the /etc/inetd.conf file. In order for the > changes to take effect the machine had to be rebooted. > > Is this the wrong approach. Is there a way for changes in >

Re: inetd & inetd.conf

2004-06-29 Thread Stephen Mulcahy
trying kill -HUP you can find the pid of the inetd by running ps -aux | grep -i inetd hth -stephen On 29 Jun 2004 12:23:22 +0100, Keith O'Connell <[EMAIL PROTECTED]> wrote: > > Hi, > > I just had to edit the /etc/inetd.conf file. In order for the > changes to take effect the

Re: inetd & inetd.conf

2004-06-29 Thread John Summerfield
Keith O'Connell wrote: "RA" == Ronny Aasen <[EMAIL PROTECTED]> writes: RA> On Tue, 2004-06-29 at 13:23, Keith O'Connell wrote: >> I just had to edit the /etc/inetd.conf file. In order for the >> changes to take effect the machine had to be rebooted. >> >> Is this the wro

Re: inetd & inetd.conf

2004-06-29 Thread Keith O'Connell
> "RA" == Ronny Aasen <[EMAIL PROTECTED]> writes: RA> On Tue, 2004-06-29 at 13:23, Keith O'Connell wrote: >> I just had to edit the /etc/inetd.conf file. In order for the >> changes to take effect the machine had to be rebooted. >> >> Is this the wrong approach. Is there a

Re: inetd & inetd.conf

2004-06-29 Thread John Summerfield
Keith O'Connell wrote: Hi, I just had to edit the /etc/inetd.conf file. In order for the changes to take effect the machine had to be rebooted. No it didn't: Dolphin:~# /etc/init.d/inetd reload Dolphin:~# -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUB

Re: inetd & inetd.conf

2004-06-29 Thread Ronny Aasen
On Tue, 2004-06-29 at 13:23, Keith O'Connell wrote: > Hi, > > I just had to edit the /etc/inetd.conf file. In order for the > changes to take effect the machine had to be rebooted. > > Is this the wrong approach. Is there a way for changes in > inetd.conf to be ena

inetd & inetd.conf

2004-06-29 Thread Keith O'Connell
Hi, I just had to edit the /etc/inetd.conf file. In order for the changes to take effect the machine had to be rebooted. Is this the wrong approach. Is there a way for changes in inetd.conf to be enacted without the need to take the machine down and up agai