This is part of The Pile, a partial archive of some open source mailing lists and newsgroups.
Subject: RH 7.0 problems
From: stevenma@uc.shu.edu
Date: Tue, 26 Sep 2000 17:13:00 -0400
Ok got a few problems after upgrading to RH 7.0 from RH 6.2 on an SMP PIII
system. My RH 6.2 system was stock apart from using qmail instead of
sendmail. Anyway, here's my problems:
1) VMWare 2.02:
- When running vmware-config.pl to compile for the new kernel it
says:
The directory of kernel headers (version 2.2.16-22) does not match your
running kernel (version 2.2.16-22smp). Consequently, even if the
compilation of the module was successful, the module would not load into
the running kernel.
Ok that's fine, but how do I fix this? Or is this something
vmware will have to do in a future update?
2) qmail and xinetd
- I'm sure xinetd is great, but it seems like a lot more work
getting it going with tcpwrappers. You now seem to have to edit every
file in /etc/xinetd.d to modify them for wrapper usage. Also qmail
doesn't work with xinetd.d, the log file claims it's "wrappered" even when
I move my hosts.allow and hosts.deny out of /etc to turn off ALL wrappers!
I have this in /etc/xinetd.d/smtp
# Converted by inetdconvert
service smtp
{
socket_type = stream
protocol = tcp
wait = no
user = qmaild
server = /var/qmail/bin/tcp-env
server_args = tcp-env /var/qmail/bin/qmail-smtpd
disable = no
}
Anything I should add to it?
Thanks!
===
Subject: Re: RH 7.0 problems
From: Gordon Messmer <yinyang@eburg.com>
Date: Tue, 26 Sep 2000 20:36:58 -0700 (PDT)
On Tue, 26 Sep 2000 stevenma@uc.shu.edu wrote:
> 1) VMWare 2.02:
...
> The directory of kernel headers (version 2.2.16-22) does not match your
> running kernel (version 2.2.16-22smp).
You can probably get away with changing
/usr/src/linux/include/linux/version.h so that the line:
#define UTS_RELEASE "2.2.16-22"
reads:
#define UTS_RELEASE "2.2.16-22smp"
Then, change it back after you're done.
> 2) qmail and xinetd
>
> - I'm sure xinetd is great, but it seems like a lot more work
> getting it going with tcpwrappers.
tcpwrappers is mostly obsoleted by xinetd. xinetd has host control built
in. Read the man page for xinetd.conf, and pay attention to the
"only_from" and "no_access" attributes.
> I have this in /etc/xinetd.d/smtp
>
> # Converted by inetdconvert
> service smtp
> {
> socket_type = stream
> protocol = tcp
> wait = no
> user = qmaild
> server = /var/qmail/bin/tcp-env
> server_args = tcp-env /var/qmail/bin/qmail-smtpd
> disable = no
> }
This is part of the xinetd faq, which you can find at
http://www.synack.net/xinetd/faq.html. You want to use:
server = /var/qmail/bin/tcp-env
server_args = /var/qmail/bin/qmail-smtpd
Although several people claim that it works, I'm not sure how that sets
the RELAYCLIENT environment variable. Let me know if you can't get it to
work. Visit http://www.orbs.org/ afterward to make sure that your machine
isn't relaying for ip's that it shouldn't.
===
Subject: Re: RH 7.0 problems
From: stevenma@uc.shu.edu
Date: Wed, 27 Sep 2000 08:53:41 -0400
The directory of kernel headers (version 2.2.16-22) does not match
> > running kernel (version 2.2.16-22smp).
>
> You can probably get away with changing
> /usr/src/linux/include/linux/version.h so that the line:
> #define UTS_RELEASE "2.2.16-22"
> reads:
> #define UTS_RELEASE "2.2.16-22smp"
Thanks, actually what I ended up doing is just installing RedHat's non smp
kernel 2.2.16-22 and compiling that as SMP. That way I get a kernel
2.2.16-22 that's smp. This isn't the first time RedHat's multiple names
for the same kernel has screwed up software I've installed.
> tcpwrappers is mostly obsoleted by xinetd. xinetd has host control built
> in. Read the man page for xinetd.conf, and pay attention to the
> "only_from" and "no_access" attributes.
Thanks, I saw that in the man pages for it, I guess it's all how you look
at it, the no_access and only_from give you nice control, but it's more
work than just one hosts.deny/hosts.allow file, and harder to remember
what you set everything to! BUT, I did notice in the faq that you can
have TCP Wrappers running with xinetd by changing the server = line to:
server = /usr/sbin/tcpd
or wherever your tcpd is. I'll try that.
> This is part of the xinetd faq, which you can find at
> http://www.synack.net/xinetd/faq.html. You want to use:
>
> server = /var/qmail/bin/tcp-env
> server_args = /var/qmail/bin/qmail-smtpd
>
> Although several people claim that it works, I'm not sure how that sets
> the RELAYCLIENT environment variable. Let me know if you can't get it to
> work. Visit http://www.orbs.org/ afterward to make sure that your machine
> isn't relaying for ip's that it shouldn't.
I see, I'll give that a shot and see what happens. Qmail wouldn't even
show up when you telnetted to port 25 before, maybe this will fix
it. Thanks again for all your help!
===