Complete.Org: Mailing Lists: Archives: linux-help: June 2001:
[linux-help] Re: inetd and xinetd
Home

[linux-help] Re: inetd and xinetd

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: linux-help@xxxxxxxxx
Subject: [linux-help] Re: inetd and xinetd
From: Greg House <ghouse@xxxxxxxxxxxxx>
Date: Mon, 4 Jun 2001 20:21:18 -0500
Reply-to: linux-help@xxxxxxxxx

I was also talking about RedHat 6.2. I verified my configuration today and 
found that I was using inetd (inetd-0.16-4), not xinetd. I'd used xinetd on a 
different system, I guess. Sorry for the misinformation.

Greg

On Friday 01 June 2001 22:39, you wrote:
> I am talking about RH6.2. My RH7.1 has xinetd default, including a
> /etc/xinetd.d directory full of scripts (xinetd.conf then just points to
> it), which the 6.2 rpm doesn't seem to set up. But then it doesn't
> provide the good conversion either from inetd.conf to xinetd.conf, and
> it doesn't supercede inetd once installed....necessitating the weirdness
> described. IMHO, rpm in this example is rather blunt and ignorant. BTW
> the "..../rc3.d/S50xinetd" is just a link back to /etc/init.d/xinetd (as
> are the other .../rc* scripts), but the error message on boot mentioned
> ..../rc3.d/S50xinetd specifically. Does that mean it didn't try to do
> anything with S50xinetd in the other rc*'s until rc3.d? Somewhat
> mysterious to this beginner. This whole exercise was just to be able to
> properly follow a sockets tutorial that wanted xinetd. I'm no sys guru
> and I don't know my Linux boot that well. Much to learn....
>
> Greg House wrote:
> >That's very strange. I didn't have to do any of that stuff to get mine
> >working. I'll check what's on my machines when I go back to work next
> > time.
> >
> >Greg
> >
> >On Friday 01 June 2001 10:59, you wrote:
> >>This has been a hack. First, I got a RH6.2 xinetd-2.1.8.8-0.9.i386.rpm,
> >>ran it, but it didn't come with the perl script to convert inetd.conf to
> >>xinetd.conf. itox is supposedly too primitive, and in fact it was. I
> >>uninstalled it. Next, I got xinetd-2.1.8.9pre15.tar.gz, built and
> >>installed it, and it did have xconv.pl. But it wouldn't run because the
> >>author used C-style commenting. Fixed it, ran it, got the xinetd.conf
> >>finally. But I had no init scripts. Reinstalled the xinetd...rpm, which
> >>had said scripts (5 or 6 scattered about), then uninstalled original
> >>inetd...rpm. Booting, it chokes on xinetd. I see error messages in
> >>..../rc3.d/S50xinetd. Comment out "offending" code (final case default),
> >>reboot, see xinetd starting, test a few protocols: it works! But I still
> >>have no great idea what a proper xinetd is. I suppose I could reinstall
> >>the later ...9pre15. Does Debian do a better job with this sort of stuff?
>
> ----------------
> had there been two compoSers You might haVe
> asked the other one to wrIte your music.
> i'm gLad i was the onLy one Around
>                                  John Cage
>
>
>
> -- This is the linux-help@xxxxxxxxx list.  To unsubscribe,
> visit http://tmp2.complete.org/cgi-bin/listargate-aclug.cgi

-- 
"Wow, I didn't know being a super hero could be so painful."
-- This is the linux-help@xxxxxxxxx list.  To unsubscribe,
visit http://tmp2.complete.org/cgi-bin/listargate-aclug.cgi


[Prev in Thread] Current Thread [Next in Thread]