httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <unkn...@riverstyx.net>
Subject Re: [PATCH] LogRoot directive
Date Mon, 05 Apr 1999 05:40:43 GMT
The reason I was appending logs was 'coz I'd lost my mind temporarily, and
forgotten that the default httpd.conf ships with logs/ prepended to the
log filename.  However, you're right -- on some OS, symlinks aren't really
an option, so if you want to relocate your logs to somewhere else (drive
space, performance, whatever), then you don't have much choice.  Every
other web server that I've worked with has some kind of equivalent.

---
tani hosokawa
river styx internet


On Sun, 4 Apr 1999, Dean Gaudet wrote:

> I guess I need to ask... why?  What's wrong with putting "logs/" in front
> of all the log filenames and getting it relative to serverroot... drop a
> symlink in the filesystem? 
> 
> Oh wait, are you on a half-baked operating system? 
> 
> Dean
> 
> On Wed, 31 Mar 1999 unknown@riverstyx.net wrote:
> 
> > DESCRIPTION
> > ------------
> > 
> > this is a pretty simple little patch, but it's something that's bugged me
> > for over a year now.  i've tested it pretty thoroughly, and i've patched
> > mod_log_config, mod_log_referer, mod_log_agent, and http_log, so all the
> > logging should be fine.  
> > 
> > there's a new global variable (ap_log_root) that contains the log root
> > directory, and a function abstract (ap_log_root_relative()) that mimics
> > ap_server_root_relative().  ap_log_root is set to ap_server_root + "/logs"
> > if ap_log_root is empty when ServerRoot is processed.
> > 
> > the patch is against apache 1.3.6.
> > 
> > ---
> > tani hosokawa
> > river styx internet
> > 
> > 
> 


Mime
View raw message