public inbox for nncp-devel@lists.cypherpunks.su
Atom feed
From: John Goerzen <jgoerzen@complete•org>
To: Sergey Matveev <stargrave@stargrave•org>
Cc: nncp-devel@lists.cypherpunks.ru
Subject: Re: nncp-bundle, nncp-caller, and .seen not working?
Date: Wed, 30 Dec 2020 09:37:58 -0600 [thread overview]
Message-ID: <875z4jnw2x.fsf@complete.org> (raw)
In-Reply-To: <X+yJ5q4xgGIdOzBW@stargrave.org>
On Wed, Dec 30 2020, Sergey Matveev wrote:
> packet's header. I have fixed that in:
Thanks!
> By the way, I plan to add ability to create uncompressed
> nncp-exec
> packets. Currently nncp-exec always compresses the data inside,
> because
> originally it was used only for email transmission. I will add
> another
> plain packet type and an additional command line option for
> nncp-exec.
> Everything will stay the same and backwards compatibility with
> existing
> nncp-exec-generated packets won't break. After that I will
> create new
> release with current nncp-bundle fix and documentation updates.
Interesting! I just happened across an apparent memory leak in
nncp-exec in which it was using over 1GB of RAM. To be sure, I
may have been piping several GB of data to it. But I would expect
it to stream out the data as it is read from stdin, hopefully? I
wonder if this is related?
Thanks again for NNCP. I am really appreciating it!
- John
next prev parent reply other threads:[~2020-12-30 15:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 6:37 nncp-bundle, nncp-caller, and .seen not working? John Goerzen
2020-12-30 14:08 ` Sergey Matveev
2020-12-30 15:37 ` John Goerzen [this message]
2020-12-30 15:44 ` John Goerzen
2020-12-30 19:10 ` Sergey Matveev
2020-12-30 19:16 ` Sergey Matveev
2021-01-01 5:36 ` John Goerzen
2021-01-02 12:56 ` Sergey Matveev
2021-01-01 5:39 ` John Goerzen
2021-01-02 13:04 ` Sergey Matveev
2021-01-06 17:15 ` Sergey Matveev
2021-01-06 18:55 ` Sergey Matveev
2021-01-07 17:56 ` John Goerzen