head	1.15;
access;
symbols;
locks; strict;
comment	@# @;


1.15
date	2007.06.08.14.11.25;	author ossp;	state Exp;
branches;
next	1.14;
commitid	Cvh2le41PXT9f7ls;

1.14
date	2005.10.03.09.39.10;	author rse;	state Exp;
branches;
next	1.13;

1.13
date	2005.02.18.10.37.03;	author rse;	state Exp;
branches;
next	1.12;

1.12
date	2004.04.26.13.21.18;	author ossp;	state Exp;
branches;
next	1.11;

1.11
date	2004.02.17.09.16.05;	author thl;	state Exp;
branches;
next	1.10;

1.10
date	2003.11.10.19.04.53;	author rse;	state Exp;
branches;
next	1.9;

1.9
date	2003.11.06.11.07.41;	author ms;	state Exp;
branches;
next	1.8;

1.8
date	2003.06.30.14.39.09;	author ossp;	state Exp;
branches;
next	1.7;

1.7
date	2002.10.11.16.06.12;	author rse;	state Exp;
branches;
next	1.6;

1.6
date	2002.10.02.12.44.38;	author rse;	state Exp;
branches;
next	1.5;

1.5
date	2002.08.11.13.49.12;	author rse;	state Exp;
branches;
next	1.4;

1.4
date	2002.07.30.19.52.00;	author rse;	state Exp;
branches;
next	1.3;

1.3
date	2002.07.13.20.09.26;	author rse;	state Exp;
branches;
next	1.2;

1.2
date	2002.02.15.11.57.42;	author rse;	state Exp;
branches;
next	1.1;

1.1
date	2002.02.13.16.35.07;	author rse;	state Exp;
branches;
next	;


desc
@@


1.15
log
@release OSSP l2 0.9.13
@
text
@
#use wml::ossp area=pkg:lib subarea=l2

<title>OSSP l2</title>

<h1>Flexible Logging</h1>

<h2>Abstract</h2>

OSSP l2 is a C library providing a very flexible and sophisticated Unix
logging facility. It is based on the model of arbitrary number of channels,
stacked together in a top-down data flow tree structure with filtering
channels in internal nodes and output channels on the leave nodes.

<p>
Channel trees can be either constructed manually through lower-level API
functions or all at once with a single API function controlled by a compact
syntactical description of the channel tree. For generating log messages a
printf-style formatting engine is provided which can be extended through
callback functions. The data flow inside the channel tree is controlled by
(eight fixed and nine custom) logging message severity levels which are
assigned to each individual channel.

<p>
Channels are implemented by channel handlers which can be even customer
supplied for creating own channels which seamlessly integrate into the
framework. For convenience reasons, OSSP l2 already ships with pre-implemented
filtering (noop, filter, prefix, buffer) and output (null, fd, file, pipe,
socket, syslog, smtp) channels which already cover mostly all use cases of
logging.

<h2>Authors</h2>

<pkg_author name="Ralf S. Engelschall" mail="rse@@engelschall.com">
<pkg_author name="Thomas Lotterer" mail="thomas@@lotterer.net">
<pkg_author name="Michael Schloh v. Bennewitz" mail="michael.schloh@@cw.com">

<h2>Status</h2>

<pkg_status
    name="l2" assign="rse"
    stable="none"    stable_date="none"
    unstable="0.9.13" unstable_date="08-Jun-2007"
	done=95>

<h2>Source</h2>

<pkg_files 
    cvs=$(CVS_ROOT_URL)/pkg/lib/l2/
    url=$(FTP_ROOT_URL)/pkg/lib/l2/
    directory=$(FTP_ROOT_DIR)/pkg/lib/l2/
    files="l2-*.tar.gz" 
	stable="none" unstable="l2-0.9.13.tar.gz">
	
<h2>Donation</h2>

<pkg_donation name="l2" return="$(BASE_URL)/pkg/lib/l2/">

@


1.14
log
@release a bunch of OSSP libraries
@
text
@d43 1
a43 1
    unstable="0.9.11" unstable_date="03-Oct-2005"
d53 1
a53 1
	stable="none" unstable="l2-0.9.11.tar.gz">
@


1.13
log
@release OSSP l2 0.9.10 and OSSP cfg 0.9.9
@
text
@d43 1
a43 1
    unstable="0.9.10" unstable_date="18-Feb-2005"
d53 1
a53 1
	stable="none" unstable="l2-0.9.10.tar.gz">
@


1.12
log
@bulk update versions
@
text
@d43 1
a43 1
    unstable="0.9.8" unstable_date="23-Apr-2004"
d53 1
a53 1
	stable="none" unstable="l2-0.9.8.tar.gz">
@


1.11
log
@correct spelling: privileges, convenient;
@
text
@d43 1
a43 1
    unstable="0.9.5" unstable_date="10-Nov-2003"
d53 1
a53 1
	stable="none" unstable="l2-0.9.5.tar.gz">
@


1.10
log
@release OSSP sa 1.1.0, OSSP cfg 0.9.1 and OSSP l2 0.9.5
@
text
@d27 1
a27 1
framework. For convinience reasons, OSSP l2 already ships with pre-implemented
@


1.9
log
@Correct attribution
@
text
@d35 1
a35 1
<pkg_author name="Thomas Lotterer" mail="thomas.lotterer@@cw.com">
d43 1
a43 1
    unstable="0.9.2" unstable_date="30-Jun-2003"
d53 1
a53 1
	stable="none" unstable="l2-0.9.2.tar.gz">
@


1.8
log
@new fsl/l2
@
text
@d35 1
@


1.7
log
@release OSSP l2 0.9.1
@
text
@d42 1
a42 1
    unstable="0.9.1" unstable_date="11-Oct-2002"
d52 1
a52 1
	stable="none" unstable="l2-0.9.1.tar.gz">
@


1.6
log
@use bug reporting and manpage rendering
@
text
@d42 1
a42 1
    unstable="0.9.0" unstable_date="30-Jul-2002"
d52 1
a52 1
	stable="none" unstable="l2-0.9.0.tar.gz">
@


1.5
log
@flush the work of this afternoon: PayPal support, cleanups, etc
@
text
@d40 1
@


1.4
log
@release OSSP l2 0.9.0 and OSSP l2 0.9.0
@
text
@d53 4
@


1.3
log
@add CVS references
@
text
@d41 2
a42 2
    unstable="none"  unstable_date="none"
	done=80>
d51 1
a51 1
	stable="none" unstable="none">
@


1.2
log
@fix l2 page
@
text
@d47 1
@


1.1
log
@Wohhoooo! First cut for our long awaited OSSP website...
@
text
@d6 46
a51 10
The OSSP lmtp2nntp program is an LMTP service for use in conjunction
with an MTA (like Sendmail), providing a reliable real-time mail to news
gateway. Input messages get their headers slightly reformatted to match
Usenet news article format. The article is then posted or feeded into a
remote NNTP service (like INN). Delivery must take place immediately or
the transaction fails. OSSP lmtp2nntp relies on the queuing capabilities
of the MTA in order to provide a fully reliable service. For this the
program returns proper delivery status notification which indicates
successful completed action, persistent transient failure or permanent
failure.
@