[Xastir] Xastir leaking (socket) file descriptors?

[Tapio Sokura]

J. Lance Cotton wrote:
> On Wed, 03 Nov 2004 23:05:34 +0200, Tapio Sokura <oh2kku at iki.fi> wrote:
> 
>>xastir    31869  oh2kku 1015u  sock        0,0             1910852 can't
>>identify protocol

> Those are ax.25 connections, right?

There is no AX.25 support compiled into the Linux kernel and Xastir I'm 
using, so there are no native AX.25 devices either. I added a "Serial 
KISS TNC" (TM-D700) to the setup a while ago though, it is visible as 
/dev/ttyS1 in the lsof output. So in total there are two interfaces, one 
kiss tnc and one Internet feed.

Hmmh, I just remembered, that I have compiled festival support into 
Xastir as well, but I am not running festival. When I run Xastir from a 
terminal, I get those

festival_client: connect to server failed

errors printed to the screen with regular intervals, as is expected 
since I don't have festival running. I counted the number of festival 
errors printed to the console since Xastir startup and compared that 
with the number of those funny open files shown by lsof and they seem to 
match. Do we have a winner? I also had festival support compiled into 
the previous Xastir CVS version I had and got those same errors printed 
to stderr, but it never ate up the file descriptors.

   Tapio