Dave,

I tried it all and it did not work. Could it be that I have to do something
to the firewall? My network is set up as so:

DSL cable modem which connects to my router / firewall which connects to win
98 machine and a duelboot w2k server/RH linux 8.0 machine
----- Original Message -----
From: "Dave Young" <[EMAIL PROTECTED]>
To: "John Salamone" <[EMAIL PROTECTED]>
Sent: Wednesday, January 22, 2003 6:56 PM
Subject: Re: XINETD


John, don't sweat it.. it'll make sense after you play with it for a bit.

lets start from scratch.

first, make sure xinetd start when you reboot (xinetd is *really* what runs
telnet, echo and a bunch of other things, if you want to see what it
controls
look at /etc/xinetd.d/) so xinetd must start in order for telnet, etc. to
also run.

so:

chkconfig xinetd on (it's OK to do it again, and if it just comes back to
the
command prompt that means it was successful (intuitive I know)

now lets turn on telnet.

chkconfig telnet on

chkconfig also starts the service when you type this, and ALSO makes it so
it
turns on when you reboot, which is important :)


that's about it, telnet should work now. If it doesn't the firewall that
comes
w/ redhat may be blocking it (and this one is a little more complicated,
I'll
help you if this comes up)


that make a little better sense?


--Dave


On Wednesday 22 January 2003 3:47 pm, you wrote:
> Dave,
>
> So what am I suppose to be typing: CHKCONFIG XINETD ON ? If so, the what.
I
> come back to the command prompt.
> Please bare with me as I am new to linux. Thanks for your help.
> ----- Original Message -----
> From: "Dave Young" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, January 22, 2003 6:37 PM
> Subject: Re: XINETD
>
> > On Wednesday 22 January 2003 3:28 pm, Dave Young wrote:
> > > chkconfig xinetd on ; kill -HUP `cat /var/run/xinetd.pid`
> >
> > assuming it's running already. turn it on so next time we boot... but
for
>
> now
>
> > re-read the config.
> >
> > > is one of the few ways to do this.
> > >
> > > "chkconfig <daemon> on" basically creates a symlink from
> > > /etc/init.d/<daemon> to /etc/rc.d/rc.2/S##<daemon>
> >
> > rc.d/rc2.d that is
> >
> >  so when "init" comes
> >
> > > through that dir (on boot)
> >
> > well, when entering that run level
> >
> > <snip>
> >
> > Dave, get your posts right.  ;)
> >
> >
> >
> >
> >
> >
> > --
> > redhat-list mailing list
> > unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
> > https://listman.redhat.com/mailman/listinfo/redhat-list




-- 
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to