state of Lire in today's CVS

[Joost van Baal]

Hi,

I've been playing with Lire from today's CVS.

FYI: When having this in your ~/.lire/config/lire.xml :

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE config PUBLIC
  "-//LogReport.ORG//DTD Lire Report Configuration Markup Language
V1.0//EN"
  "http://www.logreport.org/LRCML/1.0/lrcml.dtd"[
<!ENTITY % LIRE.pfx "">
]>
<config xmlns="http://www.logreport.org/LRCML/">
  <global>
    <param name="lr_debug">yes</param>
    <param name="lr_logging_method">stderr</param>
    <param name="output_encoding">ascii</param>
    <param name="lr_logging_tag">lire</param>
    <param name="lr_period">weekly</param>
    <param name="lr_sql_archive">no</param>
    <param name="lr_mail_to">joostvb</param>
    <param name="lr_mail_subject">hibou at nagy</param>
    <param name="lr_sql_max_size">10</param>
    <param name="lr_old_service_aliases_file">no</param>
    <param name="log_file">no</param>
    <param name="lr_dbi_uri">no</param>
    <param name="lr_dbi_passwd_file">no</param>
    <param name="lr_dbi_user">no</param>
    <param name="lr_service">no</param>
    <param name="lr_filter">no</param>
    <param name="logsources">no</param>
    <param name="lr_xslt_processor">xsltproc</param>
</global>
</config>

Lire as build from CVS kinda works.  When some of these variables are
unset, Lire fails miserably.

BTW: Shouldn't lr_run source defaults, instead of relying on
lr_environment?

Bye,

Joost

-- 
.    .                                        http://logreport.com/
| '.|                        /^LogReport$/
| Lire                                        http://logreport.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.logreport.org/pipermail/development/attachments/20040306/df47217c/attachment.bin