Checker directive - debug info

[Dick Middleton]

On 06/23/12 19:34, Dick Middleton wrote:
> On 06/23/12 18:20, Dick Middleton wrote:
> 
>>         3. puts funny characters in logger
> 
>> I'm going to hack the logger bits out of mandos and create a test program.
>> I'll let you know what happens!
> 
> Item 3 seems to be to do with unicode_literals in the statement
> 
> from __future__ import (division, absolute_import, print_function
>                         unicode_literals)


More info:
   It's not entirely gone away:

Jun 23 19:18:20 rpi Mandos [2343]: INFO: Starting checker 'true' for Penguin-DSA
Jun 23 19:18:20 rpi Mandos [2343]: INFO: Checker for Geronimo-DSA succeeded
Jun 23 19:18:20 rpi Mandos [2343]: INFO: Checker for Penguin-DSA succeeded
Jun 23 19:18:54 rpi Mandos [2391]: INFO: TCP connection from:
('fe80::20a:cdff:fe1c:7cd0%eth0', 43125, 0, 2)
Jun 23 19:18:54 rpi Mandos [2391]: DEBUG: Pipe FD: 15
Jun 23 19:18:54 rpi Mandos [2391]: DEBUG: Protocol version: '1\r\n'
Jun 23 19:18:54 rpi Mandos [2391]: DEBUG: Handshake succeeded

The lines which do this pass explicitly unicode strings to logger e.g:
            logger.info("TCP connection from: %s",
                        unicode(self.client_address))


Regarding 2. pickle file - I think I misunderstood; this file doesn't exist
when mandos is running.  Is that right?  It's read and deleted then written
again when mandos terminates.  So it's probably been working all along.


Regarding 3.

> See, that's odd.  Twelve lines before that, a child process *was*
> started, as logged by the debug message.  Even if the subprocess exited
> before this line, there ought to have been a zombie process with the
> exit status for waitpid() to read.  So I don't see how this could ever
> happen.  I've added code to check for this in the latest trunk, though.

"If anything just cannot go wrong, it will anyway." - Murphy's Law

I replaced :/true with sleep 1 and it's still going strong.  I think you're
right it's a race condition. The test is completing before you can get to
check for it.  Probably aggravated by the very slow processor.

That's enough for me today. At least it's not all a total mystery anymore.

Thanks for your help

Dick