> Read the inetd man page and compare the suggested entry to the syntax > required by your inetd. If they differ, you'll have to figure out the > necessary adjustments from the man page or perhaps by posting a > message here. Now THAT is very useful. I made another mistake. I posted this problem at the time on this mailing list questioning wether something might be different about my particular Linux (Linux Mandrake - Redhat with KDE) installation. At that time instead of someone, saying, "yes, there are different flavors of inetd and you need do do a man inetd on your system and see how the syntax compares with that in the installation, and btw, that should be added as a note in the installation steps as well". Instead what I got was something to the effect, "Redhat is NO different than any other setup, they should all install from the tarball if you just follow the clear instructions - there is no 'magic' about your red hat setup". My mistake was to believe that response. No magic maybe, but perhaps a different syntax in the inetd that Redhat uses. Alex Miller > -----Original Message----- > From: Dave Sill [mailto:[EMAIL PROTECTED]] > Sent: Thursday, July 01, 1999 10:37 AM > To: [EMAIL PROTECTED] > Subject: RE: Howto > > > "Alex Miller" <[EMAIL PROTECTED]> wrote: > > > >Well, I don't know what "adjustments to my inetd's needs" are. > If I recall, > >it specified that file locations of the programs, which were > correct and the > >same on my system. > > Read the inetd man page and compare the suggested entry to the syntax > required by your inetd. If they differ, you'll have to figure out the > necessary adjustments from the man page or perhaps by posting a > message here. Yes, this means you'll have to actually read and > understand the inetd.conf entry, rather than blindly cutting and > pasting. > > I'm not picking on you. I'm an experienced UNIX system administrator, > and I still blindly cut and paste on occasion..and it bites me now and > then, too. The difference between the novice and the pro is that the > pro realizes it was his mistake and the novice blames the writer of > the documentation he was following. > > >So, I guess, in that sense, I "botched" the inetd setup for smtp on my > >system. > > Look, we know qmail-smtpd *can* be run from inetd--lots of us have > done it for years. The fact that you couldn't do it implies that you > didn't do something right. That doesn't mean you're an idiot, but it > does mean you botched the installation. It *was* you who modified > inetd.conf, right? > > >What "adjustments" are required? Oh, wait, if inetd became > >unsupoorted after 1.03 why isn't it just stricken from the tarball > >docs? > > Because that change alone is not sufficient to justify creating a > qmail-1.04 or even a qmail-1.03.1. > > -Dave >
