Re: Tor 0.0.4 is out

[Niels Provos <provos@citi.umich.edu>]

On Fri, Mar 26, 2004 at 05:44:11PM -0500, Roger Dingledine wrote:
> 0.0.4 fixes a pair of assert bugs introduced in 0.0.3.
> 
> Note that 'make install' will clobber your torrc, so back it up if you've
> changed it.
> 
> tarball:   http://freehaven.net/tor/dist/tor-0.0.4.tar.gz
> signature: http://freehaven.net/tor/dist/tor-0.0.4.tar.gz.asc
> 
> Improvements since 0.0.3:
> 
> When connecting to a dirserver or OR and the network is down,
> we would crash.

This is what I get when running 0.0.4:

Mar 27 09:27:29.080 [info] connection_close_immediate(): Closing connection (fd 3, type Dir, state 2) with data on outbuf.
Mar 27 09:27:29.082 [info] connection_dir_finished_flushing(): Dir connection to router moria.mit.edu:9031 established.
Mar 27 09:27:29.083 [info] conn_close_if_marked(): Cleaning up connection (fd -1).
Mar 27 09:27:29.084 [info] connection_remove(): removing socket -1 (type Dir), nfds now 15
Mar 27 09:27:29.086 [info] connection_dir_finished_flushing(): Dir connection to router moria.mit.edu:9031 established.
Mar 27 09:27:29.088 [warn] Bug: caught sigpipe. Ignoring.
assertion "errno != EPIPE" failed: file "buffers.c", line 256, function "flush_buf"
Mar 27 09:27:29.106 [info] dnsworker_main(): dnsworker exiting because tor process died.
Mar 27 09:27:29.106 [info] dnsworker_main(): dnsworker exiting because tor process died.
Mar 27 09:27:29.106 [info] dnsworker_main(): dnsworker exiting because tor process died.
Mar 27 09:27:29.108 [info] cpuworker_main(): cpuworker exiting because tor process died.
Abort (core dumped)