From: Darryl Ross (spam_at_afoyi.com)
Date: Mon 25 Jul 2005 - 07:24:05 BST
-----BEGIN PGP SIGNED MESSAGE-----
Benoît des Ligneris wrote:
> Well, I think that this is a useful tool for the vserver project.
> We are using v_portmap as well as some others v_* scripts. After having
> installed several vserver hosts I think it is much more easy to modify
> the services than to go after every application and modify one or
> several configuration file.
> Also, it is easy to check the existing services running on a given host
> and to create the v_* scripts in order to make sure that no port
> conflict will occur between the vservers and the host. This is a general
> solution to this kind of problem whereas fixing each application
> individually can be, IMHO, a pain...
Then I would suggest that perhaps you are running too many services on
My philosophy is to keep the host as minimal as possible and run
everything inside a guest (generally one guest per service). The only
two services I run on my hosts are sshd and ntpd. Every other service
that I might want to run on the host can be run inside a guest.
I run sshd on all my machines on a non-standard port (2222 for hosts and
222 for guests) as a way of stopping my logs from filling up with
door-knock attempts which also solves the port conflict issue.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
-----END PGP SIGNATURE-----
Vserver mailing list