Does anyone know why the filesys manager calls the mpe_siInit() so early in the startup sequence before even the mpod manager?
The si manager tries to start OOB filters which require mpod manager to be started and a extended channel session to be created. This does not happen until much later in the sequence causing the first filter creation of the SI manager to fail. I am wondering if a better startup sequence might be found to prevent this. Maybe:
... so on
The data carousel module (part of the platform-independent filesys module) needs to register with the native SI database to receive PAT/PMT update notifications. See the dcThreadAsync() function in $OCAPROOT/mpe/mgr/filesysmgr/ObjectCarousel/mpe_dataCarousel.c
Your use of this web site or any of its content or software indicates your agreement to be bound by these Terms of Participation.
Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.