[osiris-devel] osiris-4.0.1 release candidate 2

[Brian Wotring]

You're right, the handler should not be calling syslog(), or anything 
like it.   I have attached a diff that should address this issue, 
reviews are very much appreciated.

Thanks emmanuel.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: md_schedule.c.diff
Type: application/octet-stream
Size: 3773 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/osiris-devel/attachments/20040504/eb5fe1cd/attachment.obj 
-------------- next part --------------


On May 4, 2004, at 6:02 PM, osiris-devel at lemmin.gs wrote:

> Hi Brian,
>
> In a previous email of mine, I said that I noticed that the scheduler
> was in a blocked waiting on a lock. This morning our 4.0.0 release MD
> was locked again.
>
> Investigation via gdb revealed that the cause is the log_info() call 
> inside
> md_schedule.c:scheduling_signal_handler() (syslog is not reentrant).
>
> emmanuel

--
     Brian Wotring ( brian at shmoo.com )
     PGP KeyID: 0x9674763D