Re: A few simple ones (I hope)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sunday, March 23, 2003 00:01, Iceic wrote:
> Hi,
>
> I've just recently install mod_log_sql into my copy of Apache 1.3.26
> running on RH 7.1
> Everything operates as well as could be expected - it even did
> everything on my first attempt
> at starting apache - my most successful mod install to date.
>
> I just had a few questions for you all regarding a few things I'd like
> to get out of mod_log_sql but
> can't seem to find the information regarding it, despite some intensive
> searching in the docs.
>
> I'm running the LogSQLMassVirtualHosting directive as I'm running apache
> in a similar fashion. This
> works fine at creating the necessary tables etc, but there's a few
> things that I'm confused on how
> to achieve, if in fact these things are achievable with the current
> version of mod_log_sql.
>
> 1- Is it possible to control what logging information is being outputted
> to the db? Most of what I can
>     find regarding this is restricted to VirtualHost directives, which I
> don't use.

See if the LogSQLTransferLogFormat directive works for you in a general 
context.  In your setup it may be fine.

> 2- I don't foresee any need for the headout, headin, notes and cookies
> tables in my application, and as such
>     I'd like to be able to tell mod_log_sql to not bother outputting
> them, as it'll just consume disk space?

Well, currently this isn't possible in the MassVirtualHosting setup; the 
module automatically creates the tables if they don't exist.  This introduces 
a little bit of clutter, I suppose, but negligible space waste.

> 3- Whilst I can appreciate that this is the way it does things, I
> thought I might ask if anyone had found a
>     way around it. In a LogSQLMassVirtualHosting environment visits to
> the site www.blah.com <http://www.blah.com/>  and blah.com are
>     recorded under two separate tables. Whilst it's possible for me to
> code the application around this I thought I might
>     just double check if there's an easy way to get this done in the
> logging process.

This is a common problem but easily fixed using UseCanonicalName -- see FAQ 
entry 4.4.1 .

Regards,
Chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+gd3UYLVoao8MjQkRAuQzAKCDc/qwqh0cCnS5Ve5Uk8toff14OwCeKWAU
yBkNlZhK7+bemvNE7NIuXN0=
=3bAW
-----END PGP SIGNATURE-----

__________________________________________________________________
Reminder: to unsubscribe, send email to <[email protected]>
with the words "unsubscribe mod_log_sql" in the body (w/o quotes).
The module homepage is http://www.grubbybaby.com/mod_log_sql/