Opened at 2010-01-11T19:46:53Z
Last modified at 2010-01-16T00:42:47Z
#895 new enhancement
add "tahoe flogtool SUBCOMMAND"
| Reported by: | warner | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | undecided |
| Component: | code-nodeadmin | Version: | 1.5.0 |
| Keywords: | logging usability | Cc: | |
| Launchpad Bug: |
Description
Foolscap#51 and Foolscap-0.2.6 (released two years ago) made it possible to run "flogtool" operations as subcommands of some other package's CLI tool. I added this specifically to enable a "tahoe flogtool" command, which would allow admins to examine incident reports in $BASEDIR/logs/incidents/ and watch a running node with "flogtool tail". Admins who have installed Foolscap directly can do all of these things with /usr/bin/flogtool, but admins who got their Foolscap code as an automatically-loaded dependency of Tahoe won't have a /usr/bin/flogtool. Those admins will only have a /usr/bin/tahoe .
So the goal is to let them run i.e. "/usr/bin/tahoe flogtool tail". This should also help with "tahoe" executables created by py2exe or py2app.
Foolscap's test_logging.py has an example of attaching flogtool subcommands to an existing CLI tool.
Change History (1)
comment:1 Changed at 2010-01-16T00:42:47Z by davidsarah
- Keywords logging usability added
