Yes, that was my general plan - but I thought I'd run the general idea by people to see if it was greatly opposed before I made a PR, ha ha.-EricOn September 26, 2018 at 2:15 PM Ervin Hegedüs wrote:Hi Eric,On Wed, Sep 26, 2018 at 01:40:05PM -0400, Eric Tamme wrote:I've done a
* On 2018 26 Sep 10:31 -0500, Thomas Beierlein wrote:
> Hi Nate,
>
> thanks for the files, they were helpful.
> I found the problem for the wrong format, but do not understand where
> the reason came from.
>
> It turns out that there is a problem in the parsing logic for the
> log lines. It
Hi Eric,
On Wed, Sep 26, 2018 at 01:40:05PM -0400, Eric Tamme wrote:
> I've done a quick change which I think will add the ability to
> configure the IP via a config directive. Can you guys eyeball
> the diff and see if it makes sense, or if I have missed anything
> major?
>
>
>
I've done a quick change which I think will add the ability to configure the IP via a config directive. Can you guys eyeball the diff and see if it makes sense, or if I have missed anything major?https://gist.github.com/etamme/5fab0f3c13717322b3abb85e8acea28f-Eric / KK0ECTOn September 26, 2018
Hi Eric,
On Wed, Sep 26, 2018 at 12:16:57PM -0400, Eric Tamme wrote:
> Hi Tom,
>
> I guess my confusion lies in the fact that, there is no way to
> specify the bind ip for the socket server to listen on.
you're right.
Tlf (and nothing more) can't run more services on same ip:port.
You can
Hi Tom,I guess my confusion lies in the fact that, there is no way to specify the bind ip for the socket server to listen on. So If I try to run multiple instances on the same machine, they will all try to bind to the same IP and port, and every instance after the first will fail to do so
Hi Eric,
Am Wed, 26 Sep 2018 10:12:29 -0400 (EDT)
schrieb Eric Tamme :
> I am looking into using TLF for a multi op field day setup. I am
> thinking of potentially running multiple instances of TLF on the same
> rasberry pi server, each in their own directory etc, but I would like
> to network
Hi Nate,
thanks for the files, they were helpful.
I found the problem for the wrong format, but do not understand where
the reason came from.
It turns out that there is a problem in the parsing logic for the
log lines. It expects to have two entries for RST sent and received. As
ARRL-FD (and
hi folks,
On Wed, Sep 26, 2018 at 04:27:29PM +0200, Thomas Beierlein wrote:
> Am Wed, 26 Sep 2018 08:54:34 +0200 schrieb Ervin Hegedüs :
>
> > when do you want to release the new version?
>
> As soon as possible. I plan to release a preview version today or
> tommorow.
sounds good,
> There
Hi all,
Am Wed, 26 Sep 2018 08:54:34 +0200
schrieb Ervin Hegedüs :
> Hi Thomas,
>
> and folks,
>
>
> On Tue, Sep 25, 2018 at 08:39:49PM +0200, Thomas Beierlein wrote:
> > Hi Nate,
> >
> > while preparing for a new tlf-1.3.1 release
>
> when do you want to release the new version?
As soon
I am looking into using TLF for a multi op field day setup. I am thinking of potentially running multiple instances of TLF on the same rasberry pi server, each in their own directory etc, but I would like to network them together to share logging etc.I see that TLF is bound to 0.0.0.0 via
* On 2018 25 Sep 09:55 -0500, Eric Tamme wrote:
> I just tested using Xterm, and the issue does not occur. I would like to be
> able to use gnome-terminal if possible though. Have you got any suggestions
> on
> how I might go about getting that figured out?
Hi Eric.
I would recommend using
Hi Thomas,
and folks,
On Tue, Sep 25, 2018 at 08:39:49PM +0200, Thomas Beierlein wrote:
> Hi Nate,
>
> while preparing for a new tlf-1.3.1 release
when do you want to release the new version?
Will be there beta version?
I just ask you, because at this weeken will be the CQ-WW-RTTY
contest,
13 matches
Mail list logo