#775: no pycrypto + authorized_keys file = failure to start?
----------------------------+-----------------------------------------------
Reporter: zooko | Owner:
Type: defect | Status: new
Priority: major | Milestone: undecided
Component: code-nodeadmin | Version: 1.4.1
Keywords: | Launchpad_bug:
----------------------------+-----------------------------------------------
Comment(by warner):
oh, I'm not sure. Having configuration problems cause a clear startup
failure might be better than having the node start but then fail to do
something later. We could wrap the import statement and emit a prettier
message, but I think I'd prefer an exception at "tahoe start" time to a
log message buried in {{{logs/twistd.log}}}.
What does the "explosion" look like?
--
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/775#comment:1>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid
_______________________________________________
tahoe-dev mailing list
[email protected]
http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev
