On Fri, Jan 24, 2003, [EMAIL PROTECTED] wrote: > I am not really convinced about the use of fsl. [...] > Re Martin, Ralf already replied to your message in a timely manner, so many details were already discussed.
Please understand that there is a strict requirement for environments with multiple OpenPKG instances running on a single machine where the logs of all applications must not be intermixed across instances. This is hard to achieve for applications that use the syslog(3) facility. The solution was to "overload" the functions provided by the standard C library with those provided by a library under our control. In early releases of OpenPKG some packages came with a fakesyslog.tar.gz file that included a quick'n'dirty hacked replacement for syslog(3). It was limited to append log information to a single file, the name of that file was a build-time option and there were limitations in the handling of syslog levels. Even worse, that fakesyslog was not a software under engineering control so the tarball was modified and copied between packages without versioning. This finally led to the problem of having different versions of fakesyslog hanging around. The OSSP fake syslog library (fsl) was introduced by OpenPKG 1.2 as the successor of the fakesyslog used in previous releases. It was designed to overcome all it's predecessors limitations. As there is essentially the same team behind OSSP and OpenPKG you can expect that fsl does perfectly fit into OpenPKG. The fsl is so important to OpenPKG that it was even declared a CORE package (see http://www.openpkg.org/releng.html), which resembles the highest level of support you can expect. We really thought twice about this (for a little one sentence story see the comment at http://cvs.openpkg.org/chngview?cn=6570 :-). Nevertheless, all the effort war initiated to support environments with multiple OpenPKG instances running on a single machine. The current fsl functionality exceeds that of the original syslog(3) facility even for single instance environments. We understand that some people prefer to have a global system level logging and want to stick with the native syslog(3) facility. So we decided to make fsl optional in the future with default to use fsl. The packages will only be modified to omit fsl build and run-time requirements and remove fsl from the linker stage. The predefined fsl configuration files and rc scripts will still be installed and cron will run the scripts to trim log files which stay empty forever. Some logfile analysis tools inside OpenPKG may fail with empty or not existent logs. The global syslog(3) must be configured separately and system logs will require manual trimming ... -- [EMAIL PROTECTED] Development Team, Operations Northern Europe, Cable & Wireless ______________________________________________________________________ The OpenPKG Project www.openpkg.org Developer Communication List [EMAIL PROTECTED]
