Re: spiped 1.5.0 released

[Frederick Akalin <akalin@gmail.com>]

Hey Colin,

I noticed that the man page still says 1.4.2. D'oh, forgot to check
when you made the release announcement!

By the way, I guess I only notice this after the fact, since that's
(one way) how I confirm that the new version is installed on my
system. However, ideally, spipe/spiped would have a -v/--version
switch that would provide a more reliable confirmation. What do you
think?

-- Fred

On Sat, Feb 21, 2015 at 10:48 PM, Colin Percival <cperciva@tarsnap.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
>
> Hash: SHA1
>
>
>
> Hi all,
>
>
>
> I have just tagged the spiped-1.5.0 source tree and uploaded the release
>
> tarball to the http://www.tarsnap.com/spiped.html .  The SHA256 hash of
>
> the release tarball is
>
>   b2f74b34fb62fd37d6e2bfc969a209c039b88847e853a49e91768dec625facd7
>
>
>
> The only change between spiped-1.4.2 and spiped-1.5.0 is that spiped-1.5.0
>
> attempts to set the TCP_NODELAY socket option on connections; this avoids
>
> punishing latencies from TCP nagling.  While this can theoretically result
>
> in an increase in bandwidth usage, half of the writes spiped performs are
>
> 1060 bytes and so the potential effect of extra TCP/IP headers, even in the
>
> worst case, is not significant.
>
>
>
> - --
>
> Colin Percival
>
> Security Officer Emeritus, FreeBSD | The power to serve
>
> Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid
>
> -----BEGIN PGP SIGNATURE-----
>
> Version: GnuPG v2
>
>
>
> iEYEARECAAYFAlTpe68ACgkQOM7KaQxqam7/tACfdqU69UeyAdo9saxJmTMwcL6f
>
> Wd4AoIyFyLgeLMLEsmBet0Zbmu8SKcm9
>
> =CEPz
>
> -----END PGP SIGNATURE-----