Thank you so much!!!. It hadn't occurred to me!!. With signals, that's nice!!. hadn't thought about it!!!. Extremely thankful for the idea...
Perhaps I will use two different signals like USR2 and USR3 for instance which I don't use for nothing else...
| ATENCIÓN: este correo se ha enviado desde fuera de la organización. No pinche en los enlaces ni abra los adjuntos a no ser que reconozca el remitente y sepa que el contenido es seguro. |
Hi egoitz,
On Wed, 6 Jul 2022, at 3:40 AM, egoitz via Info wrote:
One question. I have seen that have been able to see info needed for debugging this by launching master with -v or -vv. I would not like to have launched that way master, because it could take months for this to reproduce. I need that a user to disconnect it's sessions and to have several ones for disconnect. Does exist some way, of enabling that verbosity when you know you are "near" to need it, because you suspect the bug is going to happen again?. Or... how could I achieve for enabling verbosity when I need it?. I think I don't get that verbosity info when using debug:1 in imapd.conf... so HUP signal is discarded....
Perhaps you could use something like the attached patch. This changes master's verbosity each time it receives a SIGHUP -- it will cycle through 0, 1, 2, 3, then go back to 0 and cycle through again (-vvv is the highest verbosity that has any additional effect).
With something like this, you could wait for the problem to reproduce, then send master SIGHUPs to increase the verbosity as desired, see the extra log output, then send further SIGHUPs to cycle it back to zero when you're done.
The patch is just an example, you could do whatever you wanted here... maybe make it just alternate between 0 and whichever value is useful to you, so you only need one SIGHUP to make it verbose and another to put it back to normal.
Of course, this all depends on you mostly not using SIGHUP to reread configuration in the usual way, since doing that would now have the side effect of changing the verbosity too.
Cheers,
ellie
| ATENCIÓN: este correo se ha enviado desde fuera de la organización. No pinche en los enlaces ni abra los adjuntos a no ser que reconozca el remitente y sepa que el contenido es seguro. |
