ossp-pkg/l2/TODO 1.53 -> 1.54
--- TODO 2002/01/03 15:23:19 1.53
+++ TODO 2002/01/03 16:21:20 1.54
@@ -2,6 +2,17 @@
============
Next steps:
+
+- libl2syslog:
+ OpenPKG fakesyslog is nasty, because it doesn't provide logging
+ to multiple files or filter out some messages. Additionally the
+ application has to be restarted in order to reopen the logfile which
+ is nasty for MTAs like Postfix in case of very high loads (because
+ they start again processing the queue from scratch). What we need is a
+ new L2-based libl2syslog which maps from syslog(3) API to l2(3) API.
+ We later can add the reopen feature in L2 or sends the messages via
+ Unix Domain socket to an L2 daemon which in turn logs to targets via
+ l2tool, etc.
- signal and process handling (l2_env*)
- asynchronous channel (l2_ch_async.c)
- manual page (l2.pod)
@@ -133,10 +144,6 @@
otherwise have to rebuffer the message and append the
null terminator character.
-- An optional syslog(3) compatible API for converting syslog-only based
- applications (like sendmail) to (restricted) liblog-based applications.
- -> Des ist schon implimentiert in fakesyslog oder? (ms)
-
Spec-parsing ----------------------------------------------
- implement location tracking
@@ -153,16 +160,6 @@
- perhaps rename l2_env to l2_ctx and l2_channel_ to just l2_
- API cleanup for open semantics
-Related Projects ------------------------------------------
-- Custom libsyslog
- OpenPKG fakesyslog is nasty, because it doesn't provide logging
- to multiple files or filter out some messages. Additionally the
- app has to be restarted in order to reopen the logfile which is
- nasty for MTAs like Postfix in case of very high loads (because
- they start again processign the queue from scratch). What we need
- is a new L2-based libsyslog.a which sends the stuff via Unix Domain
- socket to an L2 daemon which in turn logs to targets via L2.
-
Documentation ---------------------------------------------
- l2_ch_buffer
How the buffer object behaves in relation to up/downstream
|
|
