Hi,
even though "Severity: serious" draws some developer attention to this
bug, having a non-blocking loop in a program and consuming CPU doesn't
justify RC status. (Or did I miss sth.?)
Good to know that there is new active upstream development, and IPv6
improvement is going on in another bug re
Package: netsed
Version: 0.01c-2.1
Severity: serious
Once Netsed has received a connection that does not issue a quick shutdown,
the program enters a tight loop:
while(read_write_sed(fsock, csock)
;
The inner function executes alternate, non-blocking reads from the
two sockets. As lo
2 matches
Mail list logo
