On Sun, Jun 29, 2003, Thomas Lotterer wrote:
> [...]
> - also, there were issues regarding prolog and epilog when rotating
> logs. I thougt i did a good job at simplyfing sendmail but ralf backed
> out my changes with no full explanation. The openssh package seems to
> use a similar logic.
> [...]
In rc.sendmail your direct usage of "@l_prefix@/etc/rc sendmail
restart" instead of the existing sendmail_signal and sendmail_start
functions I found a little bit strange. Yes, your version is a lot more
straight-forward, but it introduced the first time that an rc script
calls rc for itself. I before we do such things we should make a general
decision for those approaches. If we know that this approach works fine
and as intended with both the old rc script and the forthcoming OSSP rc
replacement and that we want to do it this way, we certainly can use
your approach as is. But I personally would prefer that the new OSSP rc
allows one to directly call %foo from %bar section with some special
syntax.
In rc.openssh I left your implementation and just fixed the path to
the logfile. There the "rc calls rc" construct was not introduced.
> - i had an idea regarding l2 to add a "jitter" option to the l2_ch_file
> which would open a file before every write and close it immediately
> after. This could ease epilog issues normally required after rotating
> the log. Of course, at the price of performance, but it's an option,
> not a requirement. I think we could finish such a minor change for
> inclusion into the OpenPKG v1.3 release.
Yes, sounds good. Feel free to implement this in OSSP l2.
> - i had an idea regarding fsl to add an extra "library" which overrides
> the "fsl" string fallback when an application calls syslog(3) with no
> prior use of openlog(3). Currently, such applications would either log
> to the "fsl" default or need to patched to include an openlog(3). The
> former is nonsense and he latter is against the fsl concept of being a
> "link time solution". Again, i think we could finish such a minor
> change for inclusion into the OpenPKG v1.3 release.
Can you explain in more detail how this extra library technically works?
Does it just contain the same symbol the libfsl.a contains, again?
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
Developer Communication List [EMAIL PROTECTED]
