[tahoe-lafs-trac-stream] [Tahoe-LAFS] #1423: support multiple log gatherers using the new multi-gatherer feature of foolscap
Tahoe-LAFS
trac at tahoe-lafs.org
Mon Jan 13 20:39:16 UTC 2020
#1423: support multiple log gatherers using the new multi-gatherer feature of
foolscap
-------------------------+-------------------------------------------------
Reporter: zooko | Owner: somebody
Type: defect | Status: closed
Priority: minor | Milestone: undecided
Component: code | Version: 1.8.2
Resolution: wontfix | Keywords: regression foolscap logging
Launchpad Bug: | configuration
-------------------------+-------------------------------------------------
Changes (by exarkun):
* status: new => closed
* resolution: => wontfix
Old description:
> Once [http://foolscap.lothar.com/trac/ticket/176 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).
New description:
Once [http://foolscap.lothar.com/trac/ticket/176 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).
--
Comment:
Instead, continue moving away from Foolscap to an HTTP-based protocol and
find other solutions to log collection requirements.
--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1423#comment:2>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage
More information about the tahoe-lafs-trac-stream
mailing list