[COMMIT LOGREPORT] package/debian README.Debian,1.26,1.27
Joost van Baal
vanbaal at users.sourceforge.net
Tue Oct 3 12:32:41 CEST 2006
Update of /cvsroot/logreport/package/debian
In directory sc8-pr-cvs6.sourceforge.net:/tmp/cvs-serv11025
Modified Files:
README.Debian
Log Message:
remove all notes about Lire versions < 2.0.1-4: we no longer support these
Index: README.Debian
===================================================================
RCS file: /cvsroot/logreport/package/debian/README.Debian,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -r1.26 -r1.27
--- README.Debian 22 Sep 2003 04:47:46 -0000 1.26
+++ README.Debian 3 Oct 2006 10:32:38 -0000 1.27
@@ -4,24 +4,13 @@
$Id$
-The local Lire useraccount issue
-================================
+The local Lire useraccount
+==========================
You might have been sent here by a debconf note. Welcome!
-
-Lire user other than 'lire'
----------------------------
-
-The Lire package <= 1.2.1-2 supported the Lire user (and the lire group) to
-have another name as 'lire'. This is no longer supported. Supporting
-non-standard names for the Lire user turned out to get too complicated.
-
-If you're upgrading from such a package, and have a non-standard Lire username,
-a new user 'lire' will be created for you. You'll have to chown the files,
-owned by the old Lire user, to the new Lire user. Files in the old Lire user's
-homedirectory should get moved the new Lire user's homedirectory. Cronjobs
-should get moved.
+Local user 'lire' not belonging to Lire package
+-----------------------------------------------
If you have a user named 'lire' on your system, not suitable for running the
Lire jobs, you are in trouble. Depending on your specific situation, it might
@@ -33,71 +22,11 @@
fail.
-Lire user not a system user
----------------------------
-
-Up to version 20020214-3 of the Lire Debian package, the Lire user was created
-using adduser(1), without using --system option. By default, this creates a
-user with its uid in the 1000-29999 range. Creating such a useraccount in a
-package conflicts with the Debian Policy Manual section 10.2.2 (see bug
-#138617). It might interfere with local system policy, e.g. on systems not
-using adduser(1) but NIS tools for local useraccount management. Furthermore,
-the lire group was not a system group.
-
-_No_ effort has been made to automatically fix this situation when upgrading
-the installed Lire package. If a non-system Lire user got created on your
-system by a previous Lire installation, and you'd like to get rid of it, you'll
-have to handle this manually.
-
-The idea is: change the UID and GID of the lire user and group to one in the
-system range (100-999 by default). Make sure all files owned by the old user
-and group get assigned to the new user and group. I'll give some hints here on
-how to achieve this.
-
-- Record the `old' Lire user's crontab: run `crontab -l' as the old user.
- (You'll need it later.) Remove the old user's crontab: run `crontab -r'.
-
-- Remove the old entry in the password file: run deluser. _Don't_ use any
- --remove-* flag. Remove the skeletal startup files from the old user's home
- directory.
-
-- If the previous step didn't remove your lire group, record the users in this
- group, and run delgroup lire. Recreate the group as a `system group' by
- running addgroup --system lire. Repopulate it with the recorded users by
- running adduser username lire for each username (except the lire user
- itself).
-
- Now create a new Lire user:
-
- adduser --system --disabled-password --shell /bin/sh --ingroup lire \
- --home /var/lib/lire --gecos "Lire" lire
-
- Add it to various groups, to be 1.1-1 compliant:
-
- adduser lire adm
- adduser lire mail
- adduser lire proxy
-
-- Hand all files from the old lire user over to the new user:
-
- chown -R lire.lire /var/lib/lire
- chown .lire /etc/lire
- chown lire.lire /etc/lire/*.local
-
- .
-
-- Run crontab -e as the new user, and recreate its crontab entry, from the
- previous recorded one.
-
-This procedure will fix the situation in most common cases.
-
-
More notes about the Lire user
-==============================
+------------------------------
Note: /etc/lire is groupwritable, groupowned by group lire. This is
-done to be able to run lr_config(1) as user lire. See below for more info
-on lr_config(1).
+done to be able to configure lire as user lire.
Rationale for adduser lire: We need a fullblown user account to be able to
create an online responder. In such a setup, the user should be able to
@@ -110,57 +39,18 @@
to get rid of this directory.
-Lire's cron jobs: new configuration in lire 1.2.1-1
-===================================================
-
-Up to lire_1.1-1 , the Debian way to run Lire involved setting up cronjobs as
-the lire user, using templates supplied by lr_config(1). Since lire_1.2.1-1 ,
-this is no longer needed: files /etc/cron.{daily,weekly,monthly}/lire are
-installed. Rationale for this is: there is no easy way to guarantee the lire
-user can read all Lire-supported log files. In the new scheme, the logs are
-read as root.
-
-Up to version 1.1-1 of this package, the lire user was added to groups adm,
-mail and proxy. The 1.2.1-1 package no longer does this.
-
-If you still prefer the lr_config(1) way, go ahead. It'll still work. If you
-aren't using it yet, run lr_config as user lire. However, you might like to
-disable some of the new-style jobs: e.g., if on your system, there is both
-/etc/default/lire.d/postfix.cfg and /etc/lire/email.weekly.postfix.1.local ,
-you'll get two weekly postfix reports. You can disable the new-style one, by
-substituting
-
- daemon=/usr/sbin/postfix
-
-by
+Lire's cron jobs
+================
- daemon=/dis/abled
-
-in /etc/default/lire.d/postfix.cfg.
-
-Be sure to add the lire user to the groups, needed to read the logs on your
-system. adm, mail and proxy will likely be enough.
-
-
-Pro's and Cons of old- and new-style cronjobs
----------------------------------------------
-
-The old-style cronjobs involved lr_cron(1), lr_config(1), files
-/etc/lire/<superservice>.<period>.<service>.<n>.local, and lire's user crontab.
-The new-style cronjobs involve lr_vendor_cron(1), files
+The Lire cronjobs use lr_vendor_cron(1), files
/etc/default/lire.d/<daemon>.cfg, and /etc/cron.<period>/lire.
-The new-style cronjob works without any manual configuration. The old-style
-one allowed more configuration: one could set e.g. the email address and
-subject. The old-style cronjob doesn't yet support all Lire services. (If
+The Lire cronjob doesn't yet support all Lire services. (If
you'd like to get another Lire service supported, create a suitable
lire.d/<daemon>.cfg file. Adding such a file to /etc/default/lire.d/ is all
you need to do to get the log processed. Please report a wishlist bug, and
sent your <daemon>.cfg file, so that other users can benefit!) The new-style
-cronjobs run the filter as root, and read the log file as root. The old-style
-one does all processing as the lire user.
-
-Decide for yourself which scheme you prefer.
+cronjobs run the filter as root, and read the log file as root.
If you don't like the default reports
@@ -172,225 +62,6 @@
instructions on how to customize these.
-Upgrading
-=========
-
-Some incompatible changes have been made to upstream Lire during its
-development. We quote the relevant bits from upstream INSTALL file (which is
-not shipped with the Debian binary package).
-
-
-Upgrading from lire 1.1-1 or earlier: weeknumbering
----------------------------------------------------
-
-Some changes have been made in upstream Lire 1.2. You'll likely get
-bit by a warning: "defaults warning obsolete LR_WEEK_STARTS_ON variable
-found. please use LR_WEEK_NUMBERING instead. see /etc/lire/defaults for
-usage." In your /etc/lire/defaults.local, change
-
- LR_WEEK_STARTS_ON=sun
-
-into
-
- LR_WEEK_NUMBERING=U
-
-. Upstream writes about this:
-
-<quote>
-
-The configuration variable used to select the way weeks are numbered (this
-affect the way weekly aggregation is done) was changed from LR_WEEK_STARTS_ON
-to LR_WEEK_NUMBERING in Lire 1.2. You can now choose between U, W and ISO (see
-comments in .../etc/lire/defaults for the meaning of these) . You'll get a
-warning if you have a LR_WEEK_STARTS_ON configuration variable set. You might
-want to inspect your .../etc/lire/defaults.local and ~/.lire/etc/defaults for
-this variable, and adjust it accordingly.
-
-</quote>
-
-Other changes will only affect you if you've made local changes to your Lire
-configuration. If this is the case, then read on.
-
-<quote>
-
-With Lire 1.2 and later you cannot process XML reports generated by a
-version 1.1 and earlier of Lire. If there is demand for it, we may
-provide a 1.0-2.0 report converter in the future. For now, you'll have to
-reprocess your old log files, if you want reporting on them.
-
-Because of the many changes to the report specifications, one can't merge new
-reports with reports generated by a previous version of Lire. If you're not
-using lr_xml_merge(1) or lr_xml2report(1) s' merging capabilities, this won't
-affect you.
-
-The summary operator is removed in Lire 1.2 (it's obsoleted by the summary
-feature of the new reporting engine). This will only affect you if you've
-written your own report definitions, and used this operator.
-
-LogML output format was dropped in Lire 1.2 (see the NEWS file for more
-information).
-
-</quote>
-
-
-Upgrading from lire 1.0-1 or earlier: the great renaming
---------------------------------------------------------
-
-When upgrading your Debian package, you'll very likely not get bitten by this
-change. However, if you've made big local modifications, read on.
-
-<quote>
-
-With Lire 1.1, some scripts changed names:
-
- bind8-query2dlf was renamed to bind8_query2dlf
- bind9-query2dlf was renamed to bind9_query2dlf
- acl_cisco_log2dlf was renamed to cisco_ios2dlf
- squid2dlf was renamed to squid_access2dlf
- ipmon2dlf was renamed to ipfilter2dlf
-
-. Locations of 2dlf convertors changed: all convertors are now installed in
-<libexecdir>/lire/convertors/ . (They used to be in
-<libexecdir>/lire/<superservice>/ .)
-
-Services were renamed:
-
- bind8 was renamed to bind8_query
- bind9 was renamed to bind9_query
- cisco was renamed to cisco_ios
- squid was renamed to squid_access
- lprng was renamed to lprng_account
- cups was renamed to cups_pagelog
-
-(lr_log2report, lr_log2mail and other command line interfaces still offer
-backwards compatibility: they still grok the old service names.)
-
-However, backward compatibility is supported only for commandline tools, not
-for online responders' lr_spoold: If you're running an online responder, you
-have to rename your mailboxen to the new servicenames manually. You might want
-to set up email aliases to offer backwards compatibility for people mailing
-their logs to your responder.
-
-lr_addresses2serviceflags and lr_getaddresses are no longer distributed with
-Lire.
-
-LR_TODLF is no longer set in etc/lire/defaults .
-
-Some user interfaces to scripts have changed: The following scripts no longer
-take a superservice argument:
-
- lr_log2mail
- lr_log2report
- lr_log2xml
- lr_processmail
-
-.
-
-The jobfiles as used by lr_cron(1) no longer need to set the superservice
-environment variable. You might want to clean up your jobfiles (these
-have names like /usr/local/etc/lire/email.daily.postfix.1.local). However,
-keeping the variable in won't harm (now).
-
-The subject of the email's send out by lr_log2mail has changed from e.g.
-
- [LogReport] email / postfix report (was: blah blah)
-
-to
-
- [LogReport] postfix report (was: blah blah)
-
-. You might want to update your procmailrc (or any other configation for
-your mailfiltering software).
-
-If you made some local extensions, you might get bitten by these change.
-
-</quote>
-
-
-Upgrading from lire 20020415-1 or earlier: changes in configuration variables
------------------------------------------------------------------------------
-names
------
-
-lire 20020214-7 is shipped with Debian woody.
-
-<quote>
-
-After Lire 20020214, a lot of environment variables have been renamed. Here's
-the list:
-
- DEBUG
- KEEP
- ARCHIVE
- FAILEDDIR
-
- SIGNATUREFILE
- DISCLAIMERFILE
- EXPLANATIONFILE
- FROM
- REPLY_TO
-
- LOGGING
- FACILITY
- LOGGERTAG
-
- DEFAULT_OUTPUT_FORMAT
- INCLUDEIMAGES
-
- JADE
- PDFJADETEX
- DBK_XML_DTD
- DBK_PRINT_STYLESHEET
- DBK_HTML_XSL
- DBK_HTML_ONEPAGE_XSL
- DBK_XHTML_XSL
- DBK_XHTML_ONEPAGE_XSL
- DBK_FO_XSL
- XSLT_PROCESSOR
- XSLTPROC
-
- CONVERT
- GZIP
- TAR
- ZIP
- SENDMAIL
-
- SERVICE
- SUPERSERVICE
- TODLF
-
- SKIP_ID_TEST
-
-All these variables have been renamed to LR_DEBUG, LR_KEEP, LR_ARCHIVE etc.
-
-The variables DEBUG and KEEP are renamed as perl variables in Lire::Config too.
-The variables SERVICE and SUPERSERVICE are renamed as perl variables in
-Lire::Program too. The variables `jobfiles_daily' and `jobfiles_weekly' are
-renamed to lr_jobfiles_daily and lr_jobfiles_weekly. The variables `TMPDIR',
-`PERL5LIB' and `XML_CATALOG_FILES' are left untouched.
-
-You will very likely have to adapt your ~/.lire/* and .../etc/lire/*.local
-files! E.g., if your /etc/lire/defaults.local reads
-
- KEEP=1
- DEBUG=
- LOGGING=stderr
-
-now, you'll have to replace it by
-
- LR_KEEP=1
- LR_DEBUG=
- LR_LOGGING=stderr
-
-.
-
-</quote>
-
-No attempt has been made to update the configuration files automatically using
-the Debian packaging system. You'll have to update /etc/lire/defaults.local,
-as written by lr_config, (and possibly some ~/.lire/* files too) manually.
-
-
Output formats
==============
--
To UNSUBSCRIBE, email to commit-request at logreport.org with a subject of
"unsubscribe". Trouble? Send an email with subject "help" to
commit-request at logreport.org
More information about the Commit
mailing list