great! I was thinking of logging the program name so that it would be easy to fix a problem if masterview was not being loaded if brought up in a new environment (not webrick, lighttpd, fcgi, scgi). The way things work we need to know the program name. However if possible I would like to find a better way that looks for something defined and not just the program name. I haven't been able to find the right thing yet. So for the apache scgi patch I just added more to the program name match.
<br><br><div><span class="gmail_quote">On 7/30/06, <b class="gmail_sendername">Deb Lewis</b> <<a href="mailto:djlewis@acm.org">djlewis@acm.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
initializer.rb method initialize_configuration(lines 715-715):<br><br> # this logging didn't seem to work??<br> # @log_msg_q << [ :info, 'Program name = '+$PROGRAM_NAME ] # log the<br>program that is starting
<br><br>That didn't work because there's still some excessively tricky<br>back-and-forth between how the initalizer gets run in the normal scenario<br>when app [rails plugin] startup loads masterview.rb and a backstop for
<br>non-standard init scenarios in which the initializer gets run explicitly.<br><br>(and reporting bad directive_path entries, the original reason I invented<br>that @log_msg_q gadget, also didn't work; ain't testing a grand idea)
<br><br>Fixed by reworking the way early-init messages are recorded and installing<br>the logger a bit earlier in the init process (do right after MV itself is<br>loaded, before the MIO init or any other startup processing)
<br><br>~ Deb<br><br><br>_______________________________________________<br>Masterview-devel mailing list<br><a href="mailto:Masterview-devel@rubyforge.org">Masterview-devel@rubyforge.org</a><br><a href="http://rubyforge.org/mailman/listinfo/masterview-devel">
http://rubyforge.org/mailman/listinfo/masterview-devel</a><br></blockquote></div><br>