support multiple log gatherers using the new multi-gatherer feature of foolscap #1423

Closed
opened 2011-06-24 22:02:09 +00:00 by zooko · 2 comments

Once Foolscap ticket #176 is fixed to accept multiple log gatherers, we could use that functionality to let Tahoe-LAFS users configure multiple log gatherers in their tahoe.cfg file.

There are some questions about dependency versioning: do we wait until the new version of foolscap is widespread and then raise the version requirement that Tahoe-LAFS has on foolscap to that version? Or do we detect whether the version of foolscap is present can handle multiple log gatherers and emit an error message with instructions to upgrade if it is not new enough and the Tahoe-LAFS user has configured multiple log gatherers?

This will fix a regression in Tahoe-LAFS (#1385).

Once [Foolscap ticket #176](http://foolscap.lothar.com/trac/ticket/176) is fixed to accept multiple log gatherers, we could use that functionality to let Tahoe-LAFS users configure multiple log gatherers in their `tahoe.cfg` file. There are some questions about dependency versioning: do we wait until the new version of foolscap is widespread and then raise the version requirement that Tahoe-LAFS has on foolscap to that version? Or do we detect whether the version of foolscap is present can handle multiple log gatherers and emit an error message with instructions to upgrade if it is not new enough and the Tahoe-LAFS user has configured multiple log gatherers? This will fix a regression in Tahoe-LAFS (#1385).
zooko added the
unknown
minor
defect
1.8.2
labels 2011-06-24 22:02:09 +00:00
zooko added this to the undecided milestone 2011-06-24 22:02:09 +00:00
davidsarah commented 2012-04-01 23:25:53 +00:00
Owner

(http://foolscap.lothar.com/trac/ticket/176) was fixed in foolscap 0.6.2.

(http://foolscap.lothar.com/trac/ticket/176) was fixed in foolscap 0.6.2.
tahoe-lafs added
code
and removed
unknown
labels 2012-04-01 23:25:53 +00:00

Instead, continue moving away from Foolscap to an HTTP-based protocol and find other solutions to log collection requirements.

Instead, continue moving away from Foolscap to an HTTP-based protocol and find other solutions to log collection requirements.
exarkun added the
wontfix
label 2020-01-13 20:39:16 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#1423
No description provided.