"Change detected, signaling reload thread" question

[Cantor, Scott]

On 8/18/11 3:31 PM, "Anna Maurer" <annam at berkeley.edu> wrote:
>The ERROR and the CRIT are understandable ­ I was still working on
>shibboleth2.xml, and wasn¹t anywhere near ready to restart the service
>and reload the file for testing. But it looks like it reloaded on its own
>when I saved the file.

Well, yes. By default it reloads on changes. If you save the file, that's
a change. It's possible to prevent that, but it's probably not even
documented.

> I checked my logs from my earlier dev work ­ I couldn¹t find the same
>lines, and I was configuring and saving shibboleth2.xml constantly. It
>looks like we were originally on 2.2.1 before the upgrade, but I can¹t
>find any release notes that indicates ³auto restart of shib service on
>shibboleth2.xml file change.²

The only difference is that with 2.4 the actual reload is on a separate
thread. It still detects and triggers the reload as a result of an attempt
to use the configuration, generally meaning when a request comes in. The
logging is different, and it's much faster handling requests during
reloads, but not the general behavior.

> 
>I¹ve confirmed it on Dev ­ any time shibboleth2.xml is saved, it will
>reload. Is this a setting in the OS or IIS manager that somehow got
>turned on? Or a function of 2.4.3?

Neither, it's default behavior going back to well before 2.0.

-- Scott