Hello, <div><br></div><div>Trying to run it on CentOS 5, I get this error:</div><div><br></div><div><div>STARTING /opt/tahoe-test/tahoe-beta/client-sftp </div><div>Traceback (most recent call last): </div>
<div> File "/opt/tahoe-test/tahoe-beta/allmydata-tahoe-1.6.1-r4470/Twisted-10.0.0-py2.4-linux-x86_64.egg/twisted/application/app.py", line 693, in run </div>
<div> runApp(config) </div><div> File "/opt/tahoe-test/tahoe-beta/allmydata-tahoe-1.6.1-r4470/Twisted-10.0.0-py2.4-linux-x86_64.egg/twisted/scripts/twistd.py", line 23, in runApp </div>
<div> _SomeApplicationRunner(config).run()</div><div> File "/opt/tahoe-test/tahoe-beta/allmydata-tahoe-1.6.1-r4470/Twisted-10.0.0-py2.4-linux-x86_64.egg/twisted/application/app.py", line 411, in run</div><div>
self.application = self.createOrGetApplication()</div><div> File "/opt/tahoe-test/tahoe-beta/allmydata-tahoe-1.6.1-r4470/Twisted-10.0.0-py2.4-linux-x86_64.egg/twisted/application/app.py", line 494, in createOrGetApplication</div>
<div> application = getApplication(self.config, passphrase)</div><div>--- <exception caught here> ---</div><div> File "/opt/tahoe-test/tahoe-beta/allmydata-tahoe-1.6.1-r4470/Twisted-10.0.0-py2.4-linux-x86_64.egg/twisted/application/app.py", line 505, in getApplication</div>
<div> application = service.loadApplication(filename, style, passphrase)</div><div> File "/opt/tahoe-test/tahoe-beta/allmydata-tahoe-1.6.1-r4470/Twisted-10.0.0-py2.4-linux-x86_64.egg/twisted/application/service.py", line 390, in loadApplication</div>
<div> application = sob.loadValueFromFile(filename, 'application', passphrase)</div><div> File "/opt/tahoe-test/tahoe-beta/allmydata-tahoe-1.6.1-r4470/Twisted-10.0.0-py2.4-linux-x86_64.egg/twisted/persisted/sob.py", line 210, in loadValueFromFile</div>
<div> exec fileObj in d, d</div><div> File "tahoe-client.tac", line 10, in ?</div><div> c = client.Client()</div><div> File "/opt/tahoe-test/tahoe-beta/allmydata-tahoe-1.6.1-r4470/src/allmydata/client.py", line 140, in __init__</div>
<div> self.init_ftp_server()</div><div> File "/opt/tahoe-test/tahoe-beta/allmydata-tahoe-1.6.1-r4470/src/allmydata/client.py", line 417, in init_ftp_server</div><div> s = ftpd.FTPServer(self, accountfile, accounturl, ftp_portstr)</div>
<div> File "/opt/tahoe-test/tahoe-beta/allmydata-tahoe-1.6.1-r4470/src/allmydata/frontends/ftpd.py", line 293, in __init__</div><div> raise AssertionError("your twisted is lacking a vital patch, see docs/frontends/FTP-and-SFTP.txt")</div>
<div>exceptions.AssertionError: your twisted is lacking a vital patch, see docs/frontends/FTP-and-SFTP.txt</div><div><br></div><div>Failed to load application: your twisted is lacking a vital patch, see docs/frontends/FTP-and-SFTP.txt</div>
<div><br></div><div>client node probably not started</div><div><br></div><div><br></div><div>Regards,</div>---<br>Wassim Drira<br><br>
<br><br><div class="gmail_quote">On Wed, Jun 9, 2010 at 17:27, Zooko O'Whielacronx <span dir="ltr"><<a href="mailto:zookog@gmail.com">zookog@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Folks:<br>
<br>
The Tahoe-LAFS volunteer hackers have done a superb job for the last<br>
few weeks, iteratively testing and refining the major new features of<br>
Tahoe-LAFS v1.7.<br>
<br>
The current version passes our comprehensive test suite on many<br>
platforms (see the Buildbot [1] especially the "Supported Platforms"<br>
section).<br>
<br>
This is officially Tahoe-LAFS v1.7.0â!<br>
<br>
The plan is that this version will become v1.7.0 final except for<br>
improving the documentation and packaging, and fixing any critical<br>
bugs that turn up.<br>
<br>
Tahoe-LAFS v1.7 is going to be a major new release, adding important<br>
features and continuing our strong tradition of reliability and<br>
compatibility.<br>
<br>
<br>
WHAT'S NEW<br>
<br>
There are three major new features (not counting various small<br>
bugfixes and improvements): SFTP support, support for non-ASCII<br>
character encodings, and Servers of Happiness.<br>
<br>
* SFTP support<br>
<br>
Your Tahoe-LAFS gateway now acts like a full-fledged SFTP server. It<br>
has been tested with sshfs to provide a virtual filesystem in Linux.<br>
Many users have asked for this feature. We hope that it serves them<br>
well! See the FTP-and-SFTP.txt document [2] to get started.<br>
<br>
* support for non-ASCII character encodings<br>
<br>
Tahoe-LAFS now correctly handles filenames containing non-ASCII<br>
characters on all supported platforms:<br>
<br>
- when reading files in from the local filesystem (such as when you<br>
run "tahoe backup" to back up your local files to a Tahoe-LAFS grid);<br>
- when writing files out to the local filesystem (such as when you<br>
run "tahoe cp -r" to recursively copy files out of a Tahoe-LAFS grid);<br>
- when displaying filenames to the terminal (such as when you run<br>
"tahoe ls"), subject to limitations of the terminal and locale;<br>
- when parsing command-line arguments, except on Windows (to be fixed<br>
on Windows in a future release)<br>
<br>
* Servers of Happiness<br>
<br>
Tahoe-LAFS now measures during immutable file upload to see how well<br>
distributed it is across multiple servers. It aborts the upload if the<br>
pieces of the file are not sufficiently well-distributed.<br>
<br>
This behavior is controlled by a configuration parameter called<br>
"servers of happiness". With the default settings for its erasure<br>
coding, Tahoe-LAFS generates 10 shares for each file, such that any 3<br>
of those shares are sufficient to recover the file. The default value<br>
of "servers of happiness" is 7, which means that Tahoe-LAFS will<br>
guarantee that there are at least 7 servers holding<br>
some of the shares, such that any 3 of those servers can completely<br>
recover your file.<br>
<br>
The new upload code also distributes the shares better than the<br>
previous version in some cases and takes better advantage of<br>
pre-existing shares (when a file has already been previously<br>
uploaded). See the architecture.txt document [3] for details.<br>
<br>
<br>
HOW TO GET STARTED<br>
<br>
Follow the instructions in the quickstart.html document [4].<br>
<br>
<br>
CAVEATS<br>
<br>
Do not be too disappointed if you discover the following performance issue.<br>
<br>
While this release makes it possible to use Tahoe-LAFS as a mostly<br>
POSIX-compliant filesystem (thanks to FUSE and sshfs), it will have<br>
very bad performance for some cases which have good performance on<br>
your traditional local filesystem. In particular it is bad at making<br>
small changes to large files (it actually stores the new file contents<br>
every time you write to the file and re-uploads the entire file every<br>
time you close it after having written to it). On the other hand it<br>
has some nice scalability and load-balancing characteristics compared<br>
to traditional POSIX filesystems—you will be able to easily add tens<br>
or hundreds of computers to your distributed, shared Tahoe-LAFS<br>
filesystem and it will take advantage of them in a nice distributed<br>
pattern without going noticeably slower than if you had a single<br>
Tahoe-LAFS server.<br>
<br>
So, you should not assume that the POSIX emulation of Tahoe-LAFS v1.7<br>
will perform sufficiently well at a particular use case or load<br>
pattern until you've tried it, but if you do try it and it does<br>
perform acceptably well then you can feel confident that it will<br>
continue to perform that well as you scale out your filesystem.<br>
<br>
Improving the performance in some dimensions is one of the goals of<br>
the Google Summer of Code Project which will result in Tahoe-LAFS v1.8<br>
this Fall (northern hemisphere).<br>
<br>
<br>
COMPATIBILITY<br>
<br>
This release continues the tradition of full backward-compatibility.<br>
Use it without fear.<br>
<br>
<br>
ENJOY!<br>
<br>
We think Tahoe-LAFS is a really cool hack with great potential. That's<br>
why we spend our time on it as a labor of love. We hope you find good<br>
uses for it.<br>
<br>
<br>
Regards,<br>
<br>
Zooko, release manager of v1.7<br>
<br>
[1] <a href="http://tahoe-lafs.org/buildbot/" target="_blank">http://tahoe-lafs.org/buildbot/</a><br>
[2] <a href="http://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/frontends/FTP-and-SFTP.txt" target="_blank">http://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/frontends/FTP-and-SFTP.txt</a><br>
[3] <a href="http://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/architecture.txt" target="_blank">http://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/architecture.txt</a><br>
[4] <a href="http://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/quickstart.html" target="_blank">http://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/quickstart.html</a><br>
_______________________________________________<br>
tahoe-dev mailing list<br>
<a href="mailto:tahoe-dev@allmydata.org">tahoe-dev@allmydata.org</a><br>
<a href="http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev" target="_blank">http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev</a><br>
</blockquote></div><br></div>