[Xastir] New Xastir port

[N1OFZ]

I updated and rebuilt Xastir this morning and didn't see much 
difference.  I decided to try something else so I got rid of KDE and 
used twm.  Sure enough I'm not seeing the problem anymore.  Seems 
strange to me that the Window/Desktop Manager would have such an effect 
on Xastir.

Dana
N1OFZ

On Aug 8, 2004, at 6:17 PM, Curt Mills wrote:

> On Sat, 7 Aug 2004, N1OFZ wrote:
>
>> Now to the next question, I have been running Xastir for a day now 
>> with
>> the new server port on and another Xastir box connected to it.  I now
>> have 170 processes showing: [xastir] <defunct>.  There are also some
>> running processes as well.  Any idea what is going on and what needs 
>> to
>> be done to clean these processes up?
>
> Sounds like something is connecting to the listener socket a lot and
> then not doing a proper disconnect, then connecting again.  Could
> also be someone doing port scanning on your box.
>
> Any process with "defunct" listed means that the process has died
> but it's parent process has not reaped the process status yet.
> Sometimes if it has been orphanes you have to wait for the "init"
> process to come along and do that.
>
> If Xastir detects that one of the forked processes has died it tries
> to do a "wait" in order to reap the process.
>
> Assuming it isn't something peculiar about your system that is doing
> it, one thing that usually works well is to set the KEEPALIVE flag
> so that Xastir tries to send some out-of-band data periodically just
> to keep a stream alive.  If a connection doesn't go end-to-end,
> Xastir will detect it at that point.
>
> -- 
> Curt, WE7U.				archer at eskimo dot com
> http://www.eskimo.com/~archer
>   Lotto:  A tax on people who are bad at math. - unknown
> Windows:  Microsoft's tax on computer illiterates. - WE7U.
> The world DOES revolve around me:  I picked the coordinate system!"
>
>