From: Guillaume R. <Gui...@in...> - 2005-03-29 14:09:03
|
Les Mikesell wrote: > On Tue, 2005-03-29 at 07:44, Guillaume Rousse wrote: >=20 >>I'm quite curious about the documentation recommending to either use=20 >>su_exec with apache running under standard id, or mod_perl with apache=20 >>running under backuppc uid. I don't see why the two questions of uid=20 >>mapping (apache vs backuppc daemon) and perl perfs are confused here.=20 >>You could as well use su_exec with mod_perl, or make apache run under=20 >>backuppc uid without mod_perl. >=20 >=20 > You can't run perl scripts under a different uid under mod_perl (or > at least you couldn't in the 1.x versions). The whole idea of mod_perl > is that it runs embedded in the httpd process and is thus much faster > than starting a normal CGI on every hit.=20 I know what mod_perl is. My point is that if you're ready to make=20 mod_perl run under backuppc uid as a whole, you could do it as well for=20 standard apache. Hence the need to distinguish between two problems, uid=20 mapping and perfs, which current documentation doesn't. You may be right about the unability to run su_exec under mod_perl howeve= r. --=20 When they ship styrofoam, what do they pack it in? -- Why Why Why n=B020 |