Difference between revisions of "VirtualMin Specific Configuration"

Revision as of 15:27, March 9, 2009

in order to make AWBS and Virtualmin work on the same IP, you need to:

1. Enter Webmin (If you're using virtualmin theme you will have to click on Webmin) 2. Go to Servers->Apache Webserver 3. Click on "Module configuration" 4. in the dropdown, choose "System Configuration" 5. Find a line "Command to apply configuration" 6. By default, it is set to restart server. change it to "Use apachectl or HUP signal", or (as I did) - enter custom command - "/etc/rc.d/init.d/httpd graceful" 7. Save

This way each time virtual host is created, apache will not restart, but just apply configuration.

How to run AWBS on Virtualmin GPL: When creating a host, AWBS will complain that "/usr/libexec/webmin/virtual-server/modify-limits.pl is not found". Although the virtual host will be created in Virtualmin, AWBS will not mark the job as complete and wont remove the job from queue. My dirty solution is to simply create the file.

vi /usr/libexec/webmin/virtual-server/modify-limits.pl

And put into it:

2. !/usr/bin/perl

print "Just a dummy output. Nothing is done.\n"; exit(0);

The file seems to be responsible for upgrading packages and adding addons. So I aasume, AWBS users will not be able to upgrade packages automatically - I will have to make the update manually.

The tricky thing seemed to be to synchronize package features in AWBS and Virtualmin. It may sound obvious, but if the module is not installed in Virtualmin and is set to "true" in AWBS package configuration - error will be raised and account not created. In particular, it is true for antivirus, antispam features (the features are not available in GPL version probably). In general the features are useless, because virus/spam check performed globally for all mail (at least in my setup).

So, now you can proudly claim that you fully support Virtualmin PRO and GPL versions. The limitations noticed above are on Virtualmin side.