Hello, This is a suggestion. I was browsing through iServer's Virtual Server Help (http://www.iserver.com/support/virtual/admin/imanager/install.html) a couple of minutes ago and the iManager section caught my attention. Here are a few things which would be good if included in the Web Administration scripts: (I would refer to the Web Administration scripts as CP in the following points) - CP Installation within each VS The CP.tar.gz file would be included in the /usr/local/contrib directory within each VS. If the customer wants a browser-based administration CP, then he would untar CP.tar.gz and install it himself. * This would save many of us the trouble of configuring mod_auth_mysql and setting the correct DB permissions, etc. - Include CP for Virtual Hosts within VS Each Virtual Host will have access to the CP - functions, etc are limited to its home directory. * More information can be obtained from the above URL. Other matters which I would like to bring to everyone's attention: - Webmin By removing the following lines from the setup.sh file included with the Webmin package, the 'admin' user will be able to install Webmin: # Only root can run this id | grep "uid=0(" >/dev/null if [ $? != "0" ]; then echo "ERROR: The Webmin install script must be run as root"; echo ""; exit 1; fi And a problem I noticed: >From within Webmin, the VS owner will be able to install Perl modules using the CPAN module in Webmin. As we know, /usr/lib is hard linked, therefore these Perl modules are actually being installed into the skel which affects all VSes. This is something that I want to confirm: I noticed that only the directories within /usr/local and /var and writable by the 'admin' user. I am unable to create /usr/local/contrib but was definitely able to create /usr/local/src/contrib. Is anyone having the same problem? Thank you very much, Zen
