suexec configured to run under /var/www ...

<div class='quote'>This whole install have been nothing but problematic I was hoping that it was a faulty install that was causing my previous mail, and cgi problems. I even used webmin to install all modules during the testing process.</div>

That's not the way to install a full Virtualmin stack. Installing Webmin modules does nothing to the underlying system--it simply can't. Webmin module packages don't have that kind of capability--they're just tarballs (though Webmin does do some dependency resolution against other Webmin modules and such).

There is an install script for Virtualmin found on the download page here at Virtualmin.com. It does a complete install of all dependencies (like Apache, BIND, Postfix, etc.) and it configures them appropriately for use with Virtualmin. Installing and configuring manually is certainly possible...but it's not something I'd suggest unless you're a pretty serious Linux nerd.

<div class='quote'>It is the public version so I guess that is a possible reason why.</div>

The install script is available for both Virtualmin GPL and Virtualmin Professional. There is quite a bit of documentation about installing Virtualmin here:

http://www.virtualmin.com/documentation/id,automatic_virtualmin_installa...

What details do you need?

I found it:
System Settings &acirc;

<div class='quote'>You're not seeing the Virtualmin software repository, because you're missing the virtualmin.repo file that points to software.virtualmin.com/gpl/ -- but that's something you can add manually.</div>

The virtualmin-universal repository is something he can add manually (and should), but it won't help him with Apache. We only provide Apache on supported operating systems...and Fedora 9 isn't a supported system for Virtualmin GPL (it is for Professional, but we still strongly discourage use of Fedora on servers).

Apache will need to be rebuilt, if you want to use suexec. Docs for that process have been posted here in the forums a few times, and I can help you find it if you don't have any luck searching for those threads.

<div class='quote'>Why is it not possible to just tell virtualmin to use what is currently setup? </div>

You can, in System Settings -&gt; Module Config -&gt; Defaults for new domains -- you can set whatever home directory you want in there, including /var/www.

The problem you'll run into is with suexec specifically. It has to be compiled with a path for which it will run. The suexec distributed with Virtualmin is compiled for /home.

So it's no problem if you want to use /var/www, but you'll need to either:

1. Disable suexec (in System Settings -&gt; Server Templates -&gt; Default Template -&gt; Apache Website, &quot;Automatically add appropriate SuExec directive&quot;.

2. Don't use Virtualmin's Apache packages, using the ones included with your distro instead

3. Compile suexec manually, pointing suexec to the location of your choice

<div class='quote'>Since Virtualmin has to do things differently</div>

Eric <i>just</i> explained that that is not true. I'm not sure how you could have interpreted his advice as being &quot;Virtualmin has to do things differently&quot;. Virtualmin is nothing if not flexible.

But, you do what you have to do. ;-)