>>> The following patch clarifies that sending "r" over the FIFO doesn't >>> produce the exact same results as SIGUSR1. Or do you prefer that we change >>> the behaviour of the FIFO's "r" to match SIGUSR1, for example by changing >>> ui_report() to something similar to ui_report_sa(); opening a file, and >>> rewrite a few _report functions to use fprintf instead of LOG_DBG()? >> >> ...aaaaand here's the patch, in the right direction >> ... > > can i ask, if you use "r" do you have to specify the filename to log to > then? note that we currently document: > > option -R: -R report-file > fifo r: r
Nope, fifo "r" doesn't support outputting to a file at the moment. It can only write to a logging channel.
