[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[dev-serveez] towards 0.2.1
From: |
Thien-Thi Nguyen |
Subject: |
[dev-serveez] towards 0.2.1 |
Date: |
Wed, 20 Mar 2013 13:47:15 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.1 (gnu/linux) |
Latest HACKING "next" looks like:
* DONE Also distribute .lz tarball.
* TODO Fix bugs.
* DONE (Guile 2) segfault in ‘guile_error’ if config file already closed
* DONE (maint) Bump Automake min vers to 1.12.2.
* DONE Add ‘--solitary’ to ‘serveez --help’ output, serveez(1).
* DONE (Guile 1.8) Import ‘(ice-9 rdelim) write-line’.
* TODO Finalize [[file:BUGS::B0018][B0018]].
* TODO Finalize [[file:BUGS::B0012][B0012]].
* Modernize Scheme code.
* DONE (string-append DIR FILE) => in-vicinity
* DONE audit/rewrite one-armed ‘if’ expressions
* DONE use ‘reverse!’ instead of ‘reverse’
* DONE use ‘fs’, (widely available) SRFI and ice-9 modules
* DONE Update manpages; include release info.
* DONE Announce planned retirement of Guile 1.3.4 support.
That is, the only TODO items are "Finalize B001[82]", reproduced here
(excerpt from BUGS):
Bug: B0018
From: Stefan Jahn <address@hidden>
State: unfixed
Date: 2000-07-01
Description: Cannot recompute the Linux kernel's checksums of larger
(larger than a single MTU, fragmented) ICMP packets. It
seems like the defragmented user level packet (IP header)
contains the checksum of the first fragment with its
length and the More-Fragments-Flag set.
Bug: B0012
From: Stefan Jahn <address@hidden>
State: unfixed
Date: 2000-09-12
Description: If the server has many open connections with much traffic
Linux starts deadlocking for some reason. This
corresponds with the occurrence of EWOULDBLOCK or EAGAIN
on network sockets. Seems that if one socket starts
this, all want to do the same: nothing but wasting time
in kernel space. Errors happen to be on outgoing
connections only.
I think these are very old bugs that manifest only on very old kernels,
but maybe that's just wishful thinking. (I haven't investigated.)
Stefan: Could you post test cases so that i might try to reproduce them?
If i can't scrounge up test cases in the next week or two, i'll change
the state to ‘cant-reproduce-wont-fix’ and release 0.2.1.
In the meantime, if anyone finds other problems (segfaults, portability,
whatever), please let me know. NB: libserveez has not changed at all.
--
Thien-Thi Nguyen
GPG key: 4C807502
pgpH2iIhJq4xa.pgp
Description: PGP signature
- [dev-serveez] towards 0.2.1,
Thien-Thi Nguyen <=