|
Check-in Number:
|
1414 | |
| Date: |
2001-Dec-08 21:58:14 (local)
2001-Dec-08 20:58:14 (UTC) |
| User: | rse |
| Branch: | |
| Comment: |
rember a few things from the past team meetings |
| Tickets: |
|
| Inspections: |
|
| Files: |
|
ossp-pkg/l2/l2.pod 1.10 -> 1.11
--- l2.pod 2001/11/16 23:00:47 1.10
+++ l2.pod 2001/12/08 20:58:14 1.11
@@ -73,6 +73,19 @@
and takes less coding effort. The channel definition language is almost
always sufficient for an application using L2.
+=head1 LOGGING LEVELS
+
+PANIC fatal error -> immediate abort (SIGBUS, SIGSEGV)
+CRITICAL temporary failure -> sleep, retry possible (malloc == NULL)
+ERROR functionality error
+WARNING functionality successful
+NOTICE operation, statistics, start/stop
+--- border line production/testing ---
+INFO step-by-step
+TRACE I/O tracing
+--- border line end-user/developer
+DEBUG debugging messages
+
=head1 CHANNEL TREE SPECIFICATION
An L2 channel tree can be descriped by a textual specification according
|
|
