In the meantime, would it work if I just ripped all the signal catchers out of Mhonarc?
(I've really made an effort to avoid touching mhonarc's code - I prefer spoons to forks - and Mhonarc's excellent callback and config system has made this totally possible. But I'd really like to get this driver working, and the signal catching seems to me tangential enough that ripping it out won't really be much of a fork - at best, an extra errand to merge when upgrading to new releases...) On 8/10/05, Earl Hood <[EMAIL PROTECTED]> wrote: > The signal handling in mhonarc is not friendly for embedded > based work, and this should be fixed. > > First, it appears that mhonarc does not properly reset signal handlers > after an archive is processed. But even if it did, this would not > help you if you send a signal during mhonarc's write operations. > > An option should be made available to disable MHonArc's signal > handling, mainly for embedded usage, causing the caller to be > responsible for any signal handling. Alternatively, mhonarc can > support caller registered handlers for specific signals. Possibly > defining callback routines for when mhonarc sets and resets signal > handlers, allowing the mhonarc caller to hook in (and hook out) > handlers for only select signals while allowing mhonarc to handle > the others. > > --ewh > > --------------------------------------------------------------------- > To sign-off this list, send email to [EMAIL PROTECTED] with the > message text UNSUBSCRIBE MHONARC-DEV > > --------------------------------------------------------------------- To sign-off this list, send email to [EMAIL PROTECTED] with the message text UNSUBSCRIBE MHONARC-DEV
