On Thu, Apr 7, 2011 at 5:36 PM, Yehuda Sadeh Weinraub <yehudasa@xxxxxxxxx> wrote: > On Thu, Apr 7, 2011 at 5:21 PM, Colin McCabe <cmccabe@xxxxxxxxxxxxxx> wrote: >> On Thu, Apr 7, 2011 at 10:09 AM, Yehuda Sadeh Weinraub >> <yehudasa@xxxxxxxxx> wrote: >>> On Thu, Apr 7, 2011 at 9:33 AM, Colin McCabe <cmccabe@xxxxxxxxxxxxxx> wrote: >>>> Hi AnnyRen, >>> ... >>>> Also, after using injectargs to change a setting related to logging, >>>> you must send the process a SIGHUP to get it to re-read its logging >>>> settings. >>> >>> I assume this is a relatively new requirement? Usually you'd send HUP >>> signal to re-read the conf file. When using injectargs, one would >>> assume that the new configuration was already updated. Moreover, >>> sending HUP signal to all your osds/mds/mons is awfully inconvenient. >>> Maybe we can just send the HUP signal in the appropriate handlers? >> >> Hi Yehuda. >> >> It's been this way for a long time, since 2009 at least. The problem >> is that there is no notification mechanism for when a configuration >> value changes. So we'll continue writing to the same logfile until >> someone informs us to re-read g_conf.logfile (or other logging >> configuration settings). >> > Right. From your original response I assumed that all things related > to logging needed that SIGHUP (e.g., setting the different log > levels), not just reloading the log file. Changing log levels doesn't require sending SIGHUP. Sorry if that was unclear. cheers, C. -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
