What virtualmin has done to my system?

4 posts / 0 new
Last post
#1 Mon, 04/07/2008 - 00:46

What virtualmin has done to my system?

I have just bought and tried to install virtualmin pro to my debian etch system. It failed (I have another thread on this) but I have other questions too: Removing Debian apache packages... I have manually compiled and installed apache from deb sources with -fstack-protector, changed www-data user to apache and most importantly suexec docroot set to /home. With the new installation: /usr/lib/apache2/suexec -V -D AP_DOC_ROOT="/var/www" -D AP_GID_MIN=100 -D AP_HTTPD_USER="www-data" -D AP_LOG_EXEC="/var/log/apache2/suexec.log" -D AP_SAFE_PATH="/usr/local/bin:/usr/bin:/bin" -D AP_UID_MIN=100 -D AP_USERDIR_SUFFIX="public_html" Why ALL THESE were changed back to orig version ? Can I change them again ?

..... postfix is already the newest version. Note, selecting postfix instead of postfix-tls postfix is already the newest version. ..... I have also set-up postfix manually before with certs and tls enabled. I need saslauthd for postfix authentication and TLS enabled. Does the above mean that it was changed back to some other configuration? How can I find out ?

It also seems that perl and other packages were (re)-installed.

How can I find out EXACTLY what changes were made to my system ?

Is there any other way to do things in a way that I have full control? Thanks to all....

Thu, 04/10/2008 - 12:58
Joe's picture

OK, so it sounds like you really wanted to do a manual installation of Virtualmin. install.sh is for installation on a freshly installed OS.

We provide a custom Apache with suexec docroot set to /home (so something is wrong if you have suexec docroot set to /var/www...I guess your box somehow ended up with the default Debian package instead of ours...). But since you want your own Apache build, you just want to replace it with your preferred package.

<div class='quote'>How can I find out EXACTLY what changes were made to my system ?</div>

virtualmin-install.log and the output on the console would have covered <i>every</i> step of the process. If you want to pick and choose which packages to install from our repositories, you don't want to use install.sh--it's purpose is to automatically install a fully functional Virtualmin stack on a fresh OS. If you want anything else, it isn't the right tool for the job. ;-)

<div class='quote'>Is there any other way to do things in a way that I have full control?</div>

Of course. Don't run install.sh. You can just add our apt-get repository to your sources list (note that the serial number and license key are the username and password for authenticating to the repo). Once that's done you can install any of our packages using apt. Configuring them will be under your full control (and thus, it'll take a bit longer to get it all configured).

If you wanted to install your own packages, but still make use of our automatic configuration script, you can grab a somewhat generic form of it from here:


This script isn't as widely used as the virtualmin-base packages found in the various repositories, and it tries to do more (since it isn't tuned to any one OS, it tries to handle all of them correctly...I think it works well on all supported platforms, but it's not heavily tested). Anyway, if you pre-installed all of your applications (like your custom Apache and Postfix) and then installed the webmin-virtual-server and webmin-virtual-server-theme packages (along with some of the other webmin-virtualmin-* packages) you could run this script and probably get a roughly complete configuration.


Check out the forum guidelines!

Thu, 04/10/2008 - 09:49

First off VM Pro stores ALL domains under /home so that is why you seem to think its suppose to be under /var/www

However when you create a new domain no cgi will be allowed to run because you have changed the way suexec is *suppose* to work.

Thu, 04/10/2008 - 09:52 (Reply to #3)

BTW -- apache2 is a custom compile for debian and all other distro's

Topic locked