-----Original Message-----
> From: Charles Cazabon [mailto:[EMAIL PROTECTED]]
> > So did I 'fat finger' setguidid somewhere in a script or did my
> daemontools
> > install fail and I just didn't realize it? Or is there another problem?
>
> It's "setuidgid", not "setguidgid".
Yeah, people keep telling me that *I* spelled it wrong but after an hour
and a half of looking at EVERY script I had edited, "setuidgid" or
"setguidgid" was no where to be found in any text file.
Turns out I didn't fat finger anywhere. I tracked the problem to the
/service/qmail-smtp/run script. I haven't isolated the problem in the
script yet but I must have mis-set a flag, misplaced a line break or
something. I gave up after a couple of hours on trying to diagnose
my faux paux.
Here's what I did to get tcpserver to run:
1. I removed the smtp file from the xinetd.d directory which was
invoking tcpwrappers through xinetd and HUP'd xinetd. (BTW,
simply removing the smtp file and rebooting...and yeah...I
know, didn't have to reboot, could have HUP'd, etc.... did
NOT allow tcpserver to "run free". I was still getting the
errors about "setguidgid" not being found in the readproctitle
log. It was only after replacing the run file with the one
from the LWQ install docs that I was able to eliminate the
the readproctitle errors.)
2. I stopped qmail.
3. I went back to the LWQ /service/qmail-smtpd/run script and
put it into play. (I was using a script sent to me by Robin
but I had modified it - hence, my fault not his)
4. I started qmail.
5. I ran `ps auxwwwwwf | grep readp` and saw there were no
readproctitle errors.
6. I ran `netstat -lp | grep smtp` and saw that tcpserver was
the daemon. (Previous invocations of the command either
showed that xinetd was running smtp or that NO smtp was
running.
7. I put a blank rcpthosts file in the /var/qmail/control directory.
8. I checked the /etc/tcp.smtp file and made sure I had my IP
addresses set in the rules the way I wanted them.
9. Restarted qmail.
10. Tested by sending a message from the allowable IP range - success.
Tested by sending a message from an outside IP range - failure.
11. Happiness
Again, my thanks to you and Lukas for pointing me in the right direction.
I'm not enough of a linux wizard yet (going on 5 days now, woohoo!) to know
how to delete xinetd. Hell, I didn't even know what xinetd was.
Scott Zielsdorf
Senior Technical Support Consultant
Computer Instruments IVR Solutions Support Group
Voice: 913.492.1888 x8862 Fax: 913.492.1483
