On Mon, May 10, 2004, Darrell Fuhriman wrote:
> [I tried submitting this to RT, but it doesn't seem to be
> working... the bug didn't show up, and I never got an e-mail
> back, although I did get the confirmation post from petitdomo.]
>
> In 8.12, sendmail does not write pidfiles for daemons which are
> only processing queues. However, rc.sendmail assumes that it does so.
>
> This is fixed in 8.13 (as well as the addition of pidfile
> locking, and removal of the pidfile on exit).
>
> I've backported the change to 8.12 and added the patch to the
> spec file.
> I've uploaded the re-bundled RPM to
> ftp://ftp.openpkg.org/contrib/00UPLOAD/sendmail-8.12.11-20040507.src.rpm
Taken over for OpenPKG-CURRENT.
Thanks for your contribution.
> ObTangent: is fsl thread-safe?
No, it isn't -- for various reasons. Fist, the syslog(3) API it has
to emulate doesn't provide any context or other handle common to all
functions in which OSSP fsl could store its own context. Hence it has to
store it in global variables. Second, even if thread local storage would
used for the OSSP fsl internal context, this means that OSSP fsl depends
on the Pthread API. This then would introduce the Pthread API into all
OSSP fsl consuming applications. This is a big no-no, because it would
change the environment of applications too dramatically (even if they
are not Pthread based theirself).
So, some time ago we decided that the best way for the future is to
split OSSP fsl into a trivial client syslog(3) emulating part and a
daemon process (similar to syslog(3) and syslogd(8)). This way we can
make OSSP fsl easily thread-safe and at the same time solve a bunch of
other basic problems.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
Developer Communication List [EMAIL PROTECTED]
