tinc - Jan 2014 - SIGINT is a bad choice for changing log levels

Guus,

I would like to ask you to reconsider using SIGINT for logging change. It?s a
pain to kill tincd when started from the command line. Ctrl-C does not work as
expected. Great for debugging perhaps, but in normal use cases, when trying to
make a connection work and test changes it?s a pain.

On BSD there is SIGINFO (29), which can be sent by pressing Ctrl-T, but I am not
sure whether that exists on all Linuxes.

Nick
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 243 bytes
Desc: Message signed with OpenPGP using GPGMail
URL:
<http://www.tinc-vpn.org/pipermail/tinc/attachments/20140116/d47c49a9/attachment.sig>

On Thu, Jan 16, 2014 at 01:00:22PM +0100, Nick Hibma wrote:
> I would like to ask you to reconsider using SIGINT for logging change. It?s
a
> pain to kill tincd when started from the command line. Ctrl-C does not work
> as expected. Great for debugging perhaps, but in normal use cases, when
> trying to make a connection work and test changes it?s a pain.
> 
> On BSD there is SIGINFO (29), which can be sent by pressing Ctrl-T, but I
am
> not sure whether that exists on all Linuxes.
I won't change the behaviour of SIGINT in tinc 1.0.x. But this is fixed in
tinc
1.1, there Ctrl-C works as expected. It also makes it much easier to debug; you
can for example just get log output for any log level from an already running
tinc daemon using this command:

tinc -n <netname> log <loglevel>

-- 
Met vriendelijke groet / with kind regards,
     Guus Sliepen <guus at tinc-vpn.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL:
<http://www.tinc-vpn.org/pipermail/tinc/attachments/20140116/cf839a65/attachment.sig>