Since I can't get my other questions answered is it at least possible to get the autostart on boot command? My path to start from terminal is:
"/usr/share/.tahoe$ tahoe start ." [email protected]: > Send tahoe-dev mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of tahoe-dev digest..." > > > Today's Topics: > > 1. Re: Strange check results (Ed Kapitein) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 16 Aug 2015 17:17:22 +0200 > From: Ed Kapitein <[email protected]> > To: [email protected] > Subject: Re: Strange check results > Message-ID: <[email protected]> > Content-Type: text/plain; charset="windows-1252"; Format="flowed" > > Hi Zooko, > > It was easy to reproduce, without repair option 7 shares, with repair no > shares. > (same file, same directory ) > > I attached the logs to the mail, because i was unable to upload it to > the pubgrid. > (shares could be placed or found on only 2 server(s). We were asked to > place shares on at least 7 server(s) such that any 3 of them have enough > shares to recover the file. (placed all 10 shares, want to place shares > on at least 7 servers such that any 3 of them have enough shares to > recover the file, sent 5 queries to 3 servers, 4 queries placed some > shares, 1 placed none (of which 1 placed none due to the server being > full and 0 placed none due to an error)) > > > Kind regards, > Ed > > On 08/16/2015 04:42 PM, Zooko Wilcox-O'Hearn wrote: >> Hrm. I don't understand why this would happen. Ed: could you try to >> reproduce this error, and then if you succeed hit the "Report a Bug" >> button on your web gateway? >> >> https://tahoe-lafs.org/trac/tahoe-lafs/wiki/HowToReportABug >> >> I guess it *could* be a bug in 1.9.2 that has subsequently been fixed, >> but I don't remember there having been any bug that would cause this >> behavior. So, I'd really appreciate it if you'd try to reproduce it. >> >> Regards, >> >> Zooko >> _______________________________________________ >> tahoe-dev mailing list >> [email protected] >> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev >> > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20150816/c67a785d/attachment.html> > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: incident-2015-08-16--14-58-08Z-wwpbjca.flog.bz2 > Type: application/x-bzip2 > Size: 58105 bytes > Desc: not available > URL: > <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20150816/c67a785d/attachment.bin> > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: incident-2015-08-16--14-58-46Z-x77nlly.flog.bz2 > Type: application/x-bzip2 > Size: 58607 bytes > Desc: not available > URL: > <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20150816/c67a785d/attachment-0001.bin> > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: twistd.log.bz2 > Type: application/x-bzip2 > Size: 14090 bytes > Desc: not available > URL: > <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20150816/c67a785d/attachment-0002.bin> > > ------------------------------ > > _______________________________________________ > tahoe-dev mailing list > [email protected] > https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev > > > End of tahoe-dev Digest, Vol 101, Issue 15 > ****************************************** > _______________________________________________ tahoe-dev mailing list [email protected] https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
