[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [gpsd-users] gpspipe crash after more than 20 hours of working.
|
From: |
Chris Kuethe |
|
Subject: |
Re: [gpsd-users] gpspipe crash after more than 20 hours of working. |
|
Date: |
Wed, 9 Sep 2015 11:05:05 -0700 |
Why are you using netcat this way? What's wrong with just connecting
to gpsd itself? Use a message queue system that can handle more
outstanding events, or maybe write to a database (sqlite or bdb would
work).
This is not a crash. The pipe can't just keep buffering data forever,
so the kernel is going to cause gpspipe to block. That in turn means
that it's not going to be reading from gpsd or doing any activity on
the tcp socket which is going to cause the socket to time out and gpsd
to drop the inactive connection.
On Wed, Sep 9, 2015 at 9:46 AM, Cuningan Re Set <address@hidden> wrote:
> Hello i am executing this command #gpspipe -r | nc -lkp 6165 &, at first all
> seems to be ok, if a connect to port 6165 and stay connected for days
> nothing abnormal happen, but if i didn't connect in more than 20 hours or so
> when connected it start sending my a lot of NMEA output and suddenly crash,
> the process gpspipe -r crash and only stay nc -lkp 6165.
> ¿Anyone use gpspipe this way and have the same problem?
>
> best regards and thanks.
--
GDB has a 'break' feature; why doesn't it have 'fix' too?