Hello!
For whatever reasons, we are using cronolog with Apache. From one of our
httpd.conf files:
CustomLog "||cronolog -p 1day -H
/data/ti/servers/apache-/example/-prod/logs/access
/data/ti/servers/apache-/example/-prod/logs/access.%Y%m%d-%H%M" combined
Note, the /absolute/ paths for the logs... To minimize the differences
between httpd.conf files of different Apache-servers (running on the
same Unix server), we'd like -- if possible -- to use relative paths.
Unfortunately, something like:
CustomLog "||cronolog -p 1day -H logs/access
logs/access.%Y%m%d-%H%M" combined
does not work, because -- unlike Apache -- cronolog does not prepend
server's directory to the relative path-names. Things work, if we
/start/ Apache in the right directory, but, upon /restart/, the current
directory is already / and cronolog simply creates /logs (at the very
top) and puts log-files in there...
Putting environment variables into CustomLog-specified command like does
not work -- they aren't interpreted by anything and we simply get a
/$DIR/logs directory created upon Apache restart.
I'm wondering, if anybody has solved this somehow already... Thanks!
-mi
