Sean,
>This is especially annoying, because as it stands aolserver logs all
>database activity (with no option to suppress.)
I know this doesn't answer the larger question but you can turn off database
logging by setting verbose to off for a given db pool. I did this to avoid
the flood of db logging we have currently.
Jeff
-----Original Message-----
From: Sean Owen [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 17, 2001 4:15 PM
To: [EMAIL PROTECTED]
Subject: [AOLSERVER] Filtering logs
All,
Is there any way, currently, to filter ns_log output?
The current aolserver docs include information about the modlog proc, which
was used to generate module-based logs. It included filtering based on
severity. This apparently has been deprecated, as modlog.tcl only contains
the cryptic remark "##modlog is gone."
The current logging facilities don't seem to have any capability to filter
the logs, even by severity. This is especially annoying, because as it
stands aolserver logs all database activity (with no option to suppress.)
This can make debugging startup procedures, which often occur among a flood
of preliminary database activity, especially cumbersome.
Is there any standard solution, other than slogging through miles of
irrelevant logs, or modifying the server?
Thanks,
Sean
