Re: [OT] [ANNOUNCE] mod_log_sqlite

[Perrin Harkins]

Matt Sergeant wrote:
> Is that any different to how it is with file logging?

I would guess it's the same, but I don't know the details of how either 
system implements locking.  I'm mostly interested because if SQLite 
works for this it might work for fast data sharing between processes as 
well (maybe as a Cache::Cache backend).

- Perrin

Re: [OT] [ANNOUNCE] mod_log_sqlite

[Tatsuhiko Miyagawa]

At Mon, 15 Apr 2002 11:32:55 -0400,
Perrin Harkins wrote:
 
> The SQLite FAQ seems to suggest that SQLite isn't very good at parallel 
> read/write situations: http://www.hwaci.com/sw/sqlite/faq.html#q6
> 
> Have you seen any problems so far?

Yep, that's what I'd expected to happen.

Without sqlite's timeout_handler function, there happen many errors
due to database locking. But with handler there seems no problem and
it just works fine in my personal website which has 10_000 hits a day.

I should give it a shot with a site with more accesses, and examine
how to rotate the log db file.

Thanks!

-- 
Tatsuhiko Miyagawa <[EMAIL PROTECTED]>

Re: [OT] [ANNOUNCE] mod_log_sqlite

[Tatsuhiko Miyagawa]

At Mon, 15 Apr 2002 17:09:43 +0100 (BST),
Matt Sergeant wrote:

> PS: Taso: you sent to [EMAIL PROTECTED], which Ask seems to have
> setup to redirect to the right address.

Yep. I've made a mistake, which Ask kindly had outsmarted ;)

-- 
Tatsuhiko Miyagawa <[EMAIL PROTECTED]>

Re: [OT] [ANNOUNCE] mod_log_sqlite

[Matt Sergeant]

On Mon, 15 Apr 2002, Perrin Harkins wrote:

> Tatsuhiko Miyagawa wrote:
> > Announcing new Apache module (written in C):
> >
> > mod_log_sqlite is an Apache logging module for sqlite database. It
> > allows you to log your HTTP stats into sqlite, then you can do queries
> > using sqlite's SQL feature (including subselects, views) to HTTP
> > statistics.
>
> The SQLite FAQ seems to suggest that SQLite isn't very good at parallel
> read/write situations: http://www.hwaci.com/sw/sqlite/faq.html#q6
>
> Have you seen any problems so far?

Is that any different to how it is with file logging?

PS: Taso: you sent to [EMAIL PROTECTED], which Ask seems to have
setup to redirect to the right address.

-- 

<:->Get a smart net

Re: [OT] [ANNOUNCE] mod_log_sqlite

[Perrin Harkins]

Tatsuhiko Miyagawa wrote:
> Announcing new Apache module (written in C):
> 
> mod_log_sqlite is an Apache logging module for sqlite database. It
> allows you to log your HTTP stats into sqlite, then you can do queries
> using sqlite's SQL feature (including subselects, views) to HTTP
> statistics.

The SQLite FAQ seems to suggest that SQLite isn't very good at parallel 
read/write situations: http://www.hwaci.com/sw/sqlite/faq.html#q6

Have you seen any problems so far?

- Perrin

[OT] [ANNOUNCE] mod_log_sqlite

[Tatsuhiko Miyagawa]

Announcing new Apache module (written in C):

mod_log_sqlite is an Apache logging module for sqlite database. It
allows you to log your HTTP stats into sqlite, then you can do queries
using sqlite's SQL feature (including subselects, views) to HTTP
statistics.

http://freshmeat.net/projects/mod_log_sqlite/

here's an excerpt from README:



mod_log_sqlite - Apache logging module to sqlite

INSTALL:

You can install this module easily via apxs magic.

  % make
  # make install
  % make clean

CONFIGURATION (summary):

1. install sqlite from http://www.hwaci.com/sw/sqlite/
2. Add following lines to your httpd.conf

LogSQLiteDBFile sqlite-logs/sqlite_log
LogSQLiteAutoChown On 

CONFIGURATION (details):

First you should install sqlite module manually. See
http://www.hwaci.com/sw/sqlite/ for details.

Then you should initialize access_log database (from 0.05, this is
optional). Note that the database file and the directory should be
writable by httpd running user ("nobody" by default).

  # mkdir /usr/local/apache/sqlite-logs
  # chown nobody:nobody /usr/local/apache/sqlite-logs
  % sudo -u nobody sqlite /usr/local/apache/sqlite-logs/sqlite_log < create_table.sql

"create_table.sql" is bundled with this module. Note that this module
automatically creates log table if there's not one, from 0.05. You can
let this moule do chown() automatically, by adding directive:

  LogSQLiteAutoChown On

Finally, simply add the following line to your httpd.conf:

  LogSQLiteDBFile sqlite-logs/sqlite_log

Table name is "access_log" by default. You can change it via
"LogSQLiteTable" directive if you want to.

  LogSQLiteTable wwwlog

From 0.05, this module supports separate database files per
VirtualHosts, which means you can even do:

  
  ServerName vh.example.com
  LogSQLiteDBFile /home/vh.example.com/logs/sqlite_log
  

That's all! Enjoy querying your access_log via VIEWs and/or sub-querys.

--
Tatsuhiko Miyagawa <[EMAIL PROTECTED]>