On Thu, Jul 11, 2013 at 03:25:36PM +0200, Anders Berggren wrote:
> > 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 
> 
> --- sbin/isakmpd/isakmpd.8.orig Thu Jul 11 14:44:58 2013
> +++ sbin/isakmpd/isakmpd.8      Thu Jul 11 14:51:52 2013
> @@ -494,13 +494,10 @@
>  .It Ic r
>  Report
>  .Nm
> -internal state to a file.
> -See the
> -.Fl R
> -option.
> -Same as when sent a
> +internal state to log destination.
> +Same output as when sent a
>  .Dv SIGUSR1
> -signal.
> +signal, except that it is not written to the same file.
>  .Pp
>  .It Ic S
>  Report information on all known SAs to the
> 

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

jmc

Reply via email to