From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
From: "Russ Cox" <rsc@swtch.com>
Date: Wed,  3 Oct 2007 21:51:00 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Message-Id: <20071004014849.69A641E8C4D@holo.morphisms.net>
Subject: [9fans] venti 
Topicbox-Message-UUID: cab2febc-ead2-11e9-9d60-3106f5b1d025

I have fixed the sync livelock bug that anothy and others reported.

To make it easier to debug problems in the future (and to inspect
your venti servers from other machines), I suggest changing your
plan9.ini from reading

	venti=/dev/sdC0/arenas

to

	venti=/dev/sdC0/arenas tcp!127.1!17034 tcp!*!8000

The two additional addresses are where venti listens for venti
and http traffic, respectively.  The defaults are tcp!127.1!17034
and tcp!127.1!8000.  Using * instead of 127.1 in the latter will
make it so the http server is accessible from other machines.
(If you want to make your venti server accessible too, change
the first address to tcp!*!17034.) The default is 127.1 for
security reasons.

Having done this, you will be able to load pages like

	http://venti:8000/proc/threads

to get a list of threads and what code they are blocked in.  And

	http://venti:8000/proc/stacks

will give the stack for each thread, much like running stacks()
in an "acid -l thread" session.

If you do encounter problems where venti appears to be
hung in some form, I would appreciate if you could save
the output of 

	http://venti:8000/proc/all

and mail it to me when reporting the problem. 

Note that although there are new venti binaries on sources,
the kernels do not yet use the new venti.  If you boot from 
a combined venti+fossil server, you will need to rebuild 
9pccpuf/9pcf yourself in order to get it.

Thanks.
Russ