man lr_spoold (Commandes) - daemon, invoking lr_spool for all services periodically
NAME
lr_spoold - daemon, invoking lr_spool for all services periodically
SYNOPSIS
lr_spoold
DESCRIPTION
lr_spoold is typically invoked from a init script after booting the system.
It should be started as
lr_run lr_spoold
under the Lire useraccount. This is used to keep an online responder running. See the Responder Installation section in the Installing Lire chapter of the Lire User Manual for details.
lr_spoold invokes lr_check_service(1) to get a list of services, which are used as addresses for an online responder. For each address $service in this list, it runs
lr_spool $spooldir lr_processmail $service
periodically. CW$spooldir gets constructed using profile_lean and the address.
Typically, spooldir is a Maildir's `new' subdirectory, like e.g.
.../var/spool/lire/$address/Maildir/new/
.
In effect, we make it possible to invoke lr_processmail with the right arguments for each message, so that logfiles in the messages get processed by the right 2dlf convertor.
SEE ALSO
lr_spool(1), lr_processmail(1)
VERSION
$Id: lr_spoold.in,v 1.15 2003/05/04 12:14:59 vanbaal Exp $
COPYRIGHT
Copyright (C) 2000, 2001, 2002 Stichting LogReport Foundation LogReport@LogReport.org
This program is part of Lire.
Lire is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program (see COPYING); if not, check with http://www.gnu.org/copyleft/gpl.html or write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111, USA.
AUTHOR
Joost van Baal <joostvb@logreport.org>