[EMAIL PROTECTED] ScriptAlias in apache2 target uid mismatch with directory or program

2006-07-13 Thread JupiterHost.Net
We built apache 2.0.58 w/ suexec and the ScriptAlias's now result in 500 errors with target uid mismatch with directory or program logged. Obviously the error is from when SuexecUserGroup is being used and do not match the ScriptAliased directory, it never will :) The thing is this worked

Re: [EMAIL PROTECTED] ScriptAlias in apache2 target uid mismatch with directory or program

2006-07-13 Thread JupiterHost.Net
JupiterHost.Net wrote: We built apache 2.0.58 w/ suexec and the ScriptAlias's now result in 500 errors with target uid mismatch with directory or program logged. Obviously the error is from when SuexecUserGroup is being used and do not match the ScriptAliased directory, it never

Re: [EMAIL PROTECTED] Can 32-bit Apache binary run on 64-bit Linux RedHat OS?

2006-07-05 Thread JupiterHost.Net
Qingshan Xie wrote: Hi, Hello, Our Linux will be upgraded to 64-bit OS but the current Apache binary was compiled in 32-bit. Can 32-bit Apache binary run on 64-bit Linux OS without any issue? Without *any* issue, not likley. You're best off recompiling apache, otherwise you'll spend

[EMAIL PROTECTED] Epoch time in Customlog

2006-05-08 Thread JupiterHost.Net
Howdy list! If I wanted to put the unix epoch time in a Customlog's format would I do it with this: %{%s}t thats how I understood the doc's use of '%...{format}t' where format is in strftime(3) format If not what would I use? TIA

[EMAIL PROTECTED] mod_logio adding %I and %O into one

2006-05-08 Thread JupiterHost.Net
Hello again :) Is there a way to get the sum of mod_logio's %I and %O into a Customlog? Assuming %I was 200 and %O was 200 I'd like to get 400 into CustomLog Of course, I could do CustomLog's and the log parsing app can add them together later with: CustomLog path.log whatever %I CustomLog

[EMAIL PROTECTED] Apache 1.3 to 2.X module porting: function name/argument/return/include changes?

2006-05-04 Thread JupiterHost.Net
In porting a module from apache 1.3 to 2.0/2.2 I'm seeing these apache specific elements: request_rec * r: static int foo (request_rec * r) r-uri r-server-server_hostname r-pool ap_getword: w = ap_getword(r-pool, dnam, '/'); /* previosuly: char *name = r-uri; ... dname = name + 2; */

Re: [EMAIL PROTECTED] Apache 1.3 to 2.X module porting: function name/argument/return/include changes?

2006-05-04 Thread JupiterHost.Net
I've commented on each one with what I have deduced so far, any insight into if I am correct or not or are missing something would be awesome :) JupiterHost.Net wrote: In porting a module from apache 1.3 to 2.0/2.2 I'm seeing these apache specific elements: request_rec * r: static int foo

[EMAIL PROTECTED] mod_logio with Apache 1

2006-02-13 Thread JupiterHost.Net
Is it possible to build Apache 1 with mod_logio (DSO or not)? If so, how? (url to documentation would be awesome!) http://httpd.apache.org/docs/2.0/mod/mod_logio.html The only references I can find are related to Apache 2. TIA!

Re: [EMAIL PROTECTED] mod_logio with Apache 1

2006-02-13 Thread JupiterHost.Net
Joshua Slive wrote: On 2/13/06, JupiterHost.Net [EMAIL PROTECTED] wrote: Is it possible to build Apache 1 with mod_logio (DSO or not)? Not as distributed. And I suspect the work to make it compile with 1.3 would be much greater than the work to upgrade your server to 2.2. It depends