0.1.0.2_RC_CVS - Unstable Builds Under NetBSD 2.0
This is a Flyspray task for the NetBSD wierdness we have been discussing on the or-talk list.
To this point in time:
- Beginning about March 30, my daily CVS builds were being unstable - for a few days they crashed upon launch
- Then on April 3 or 4, the daily CVS builds started working again... web browsing through tor dramatically increased in speed relative to builds prior to March 30
- About the same time there were many log messages. Initiated or-talk discussion...
- On the evening of April 5 (I'm in Indiana - EST for ref.) Nick Mathewson informed me he fixed part of the problem in CVS but only for the no-pthreads version of tor.
- Morning of April 6, tor was running fine and no new log messages.
- Noticed new CVS changes so updated no-pthreads - restarted tor at 0600
- Just Checked log @ April 6, 3:30PM: Apr 06 06:06:49.935 [err] Catching signal TERM, exiting cleanly. Apr 06 06:06:52.404 [notice] Tor 0.1.0.2-rc-cvs opening log file. Apr 06 11:13:53.401 [warn] circuit_receive_relay_cell(): Didn't recognize cell, but circ stops here! Closing circ. Apr 06 11:13:53.450 [warn] command_process_relay_cell(): circuit_receive_relay_cell (forward) failed. Closing. Apr 06 11:15:01.928 [err] Catching signal TERM, exiting cleanly. Apr 06 11:15:04.890 [notice] Tor 0.1.0.2-rc-cvs opening log file. Note: I do not recall restarting tor at 11:15, no new core file was generated???
- Just noticed more CVS changes, recompiled no-pthreads but have not installed and restarted ...should I?
- If I don't hear back, I probably will update and restart prior to going to sleep tonight.
[Automatically added by flyspray2trac: Operating System: BSD]
Trac:
Username: yancm
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information