 |
If you look at the CentOS.readme file in the docs, it clearly tells you to configure your apache to run as the backuppc user. I do not think that the RPM should mess with your httpd.conf file ... as there are multiple ways to run backuppc. I think this is something that the user needs to accomplish on their own by reading the docs. I guess we could configure the system so that it runs out of the box not using mod_perl and working under the apache user, and include instructions (and a sample config files) for running using mod_perl, however the documentation for backuppc says that there is a huge performance penalty for this kind of setup .. also something that I am not sure we want to do. I also do not want to try to make it run as a separate apache instance because that requires it to either run on a separate IP address or on a port other than port 80. I am not sure we want to try and do either of those things in the RPM. |
 |
I'll check on the backuppc mailing list about the use of mod_perl. I'm skeptical that this "performance drop" has any real-world consequence, and likely only affects the speed with which its web interface loads. Presumably one isn't using the web interface on a regular basis, enough for page loading speed to be a big issue. |
|
2007-10-24 19:25
|
backuppc.spec.diff (2,845 bytes) |
|
|
I've successful deployed the package using suexec. I found it necessary to let the UID "float" to above 500 and to move the web content within /var/www to meet the compile-time restrictions of suexec. A patch to the spec file illustrating the changes is attached. |
|
|
Two replies on the backuppc mailing list confirm that the mod_perl requirement is only to improve performance of the CGI management interface, not the actual backup software. Such a speedup is really only of value for a system under heavy web load by many users managing backups. Rather than deploy a config file that still requires editing of the main Apache config file, I'd recommend moving the current file to the %doc directory as an example of a mod_perl-based configuration. |
|
2007-10-24 19:32
|
|
|
|
I've attached a sample Apache config that shows how to use the system with suexec and a virtual host. |
|
|
I have been using BackupPC 3 on a CentOS 4 machine for a long time and didn't go for the mod_perl setup as that allowed us to use apache for a couple of other small things. Indeed, the mod_perl speedup is only for the web interface and I'll say it very usable without mod_perl. It may be "15x" faster when timed (as the BackupPC docs say), but when the CGI is already fast enough to begin with I don't think the requirement to run apache as backuppc (and not be able to easily use apache for other stuff) is worth it. So, my vote (if I have one) is on the 'Standard setup' instead of the 'Mod_perl setup' as the default for the rpm (see http://backuppc.sourceforge.net/faq/BackupPC.html#step_9__cgi_interface for the notes on these two methods). |
- Anonymous
