Re: [Proftpd-user] multi-VirtualHost and disabling server context:
On 07.09.06 18:57, Thomas L. Shinnick wrote:[color=blue]
> I have been given two IPs to play with on a server and I wanted
> ProFTPD to run on only those two IPs (no grabbing every IP on the
> server). I also wanted to make the configuration read as clearly as
> possible, by putting the very different configurations for each site
> into separate <VirtualHost> sections. And so I wanted to use *only*
> two <VirtualHost> sections and omit/discard/disable the server context.
> I have found what works, but I can't see where it is mentioned
> (enabling use of only <VirtualHost> sections) except cumulatively and
> What works is to specify both
> Port 0
> SocketBindTight on
> in the "server context", as in the following abridged configuration:[/color]
We've been running proftpd with such configuration for years, because of the
> I've seen mentions of SocketBindTight to avoid grabbing all IPs on a
> server. And I've seen mentions of "Port 0" to disable a particular
> section's IP use. Is the combination of these, to allow sole use of
> <VirtualHost> sections to define sites, documented explicitly
> somewhere that I've missed?[/color]
I don't think so. Maybe it's not bad idea to document this in FAQ or
Configuration guide, but afaik it's not there yes.
However when I was searching for such configuration, I've been asking on
this list about this issue, so the discussion should be in the list archives.
Matus UHLAR - fantomas, [email]email@example.com[/email] ; [url]http://www.fantomas.sk/[/url]
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
"The box said 'Requires Windows 95 or better', so I bought a Macintosh".
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
ProFTPD Users List <firstname.lastname@example.org>