Re: Forcing logging to the access log

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: users@xxxxxxxxxxxxxxxx
Subject: Re: Forcing logging to the access log
From: "Steve Swift" <steve.j.swift@xxxxxxxxx>
Date: Mon, 8 Jan 2007 12:01:49 +0000
Delivered-to: mailing list users@xxxxxxxxxxxxxxxx
In-reply-to: <e498c1660701051133g2384e49cj9c413d086b8e813@xxxxxxxxxxxxxx>
Mailing-list: contact users-help@xxxxxxxxxxxxxxxx; run by ezmlm
References: <dbd3c1650701050555p3f0eca93xb67110640ab243f@xxxxxxxxxxxxxx> <e498c1660701051133g2384e49cj9c413d086b8e813@xxxxxxxxxxxxxx>
Reply-to: users@xxxxxxxxxxxxxxxx

This is indeed exactly what I want. I added a "ForensicLog" and a corresponding "LoadModule" to the httpd.conf of my apache 2.2.2 running under my Windows system here at home and tried it out - perfect.

Now I'll have to make the corresponding change to the apache 2.0.46 (plus recent fixes) running on our RedHat server in the office. On that system I cannot find any file mod_log_forensic.* anywhere on the system, so the "Loadmodule log_forensic_module modules/mod_log_forensic.so" would fail.
Do I need just the "ForensicLog" statement, or do I need to obtain mod_log_forensic.so from somewhere?

See mod_log_forensic which is designed to handle exactly this sort of problem.

--
Steve Swift
http://www.swiftys.org.uk

References:
- Forcing logging to the access log
  - From: Steve Swift
- Re: Forcing logging to the access log
  - From: Joshua Slive

Prev by Date: creating .keytab file without using Win2003Server
Next by Date: saving userid
Previous by thread: Re: Forcing logging to the access log
Next by thread: mod_rewrite to speed up twiki
Index(es):
- Date
- Thread

[Index of Archives] [Open SSH Users] [Linux ACPI] [Linux Kernel] [Linux Laptop] [Kernel Newbies] [Security] [Netfilter] [Bugtraq] [Squid] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Samba] [Video 4 Linux] [Device Mapper]