Thank you Massim. I haven't used ChildExitScript, but I do have a question.
I want to run a thread that looks after a session database, and possibly others if the method works. Where would be the best place to start a persistent thread from? I thought about just launching a thread and using the global namespace to record it's existence. But is there a better way of doing this?
Kind regards, Scott On 30/1/24 01:16, Massimo Manghi wrote:
The ChildExitScript feature has been around ever since in the development of mod_rivet. Nonetheless the possible application of this configurable feature was evidently a corner case since no one realized that mod_rivet 3.x ignores it entirely (that's embarrassing for me, but that's it)I recently hit this regression myself and set out working on the issue. This might go in a bugfix release of mod_rivet to be released soonThere's some improvement we can do. For example we still have a GlobalInitScript configuration script which largely overlaps ChildInitScriptGlobalInitScript is meaningful only when SeparateVirtualInterps is Off and even in that case you can have the same effect using ChildInitScript which has a name whose meaning naturally complements ChildExitScriptI therefore propose to make GlobalInitScript an alias for ChildInitScript and deprecate it.-- Massimo --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
-- +-----------------------------------------------------------------------------+ |...will make the wilderness a pool of water, the dry land springs of water...| +-----------------------------------------------------------------------------+ | Scott Pitcher [email protected] | | +61-3-9008-5695 (B) SVP Technical Services | |PGP: https://gnupg.org/ ABN 79 220 496 603 | |KEY: https://pgp.mit.edu/pks/lookup?op=vindex&search=0xEDBE43639EFD884D | +-----------------------------------------------------------------------------+ DISCLAIMER: The content of this email is confidential and strictly intended only for the recipient(s) specified in the message. If you have received this message by mistake it is strictly forbidden to keep this email in any form, electronic or hard copy, or to share any part of it with any one else, without the prior, written consent of the author. If you have received this message by mistake, please let me know by replying to this email, and then destroy it and any copies. SECURITY: I prefer to send and receive confidential messages protected by PGP public key encryption. If you are willing to or are interested in protecting our email communication with PGP encryption, please refer to https://gnupg.org/.
OpenPGP_0xEDBE43639EFD884D.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
