Opened at 2007-07-01T04:02:04Z
Last modified at 2020-01-17T23:39:58Z
#72 new enhancement
Automatic detection of configuration changes.
Reported by: | nejucomo | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | undecided |
Component: | code-nodeadmin | Version: | 0.4.0 |
Keywords: | usability | Cc: | |
Launchpad Bug: |
Description
Wouldn't it be dandy if the client detected filesystem changes related to configuration (such as the creation/modification of $BASE/webport) and reacted appropriately?
Change History (5)
comment:1 Changed at 2007-07-02T19:20:21Z by warner
- Milestone set to release 1.0
comment:2 Changed at 2007-08-14T18:57:36Z by warner
- Component changed from code to code-nodeadmin
- Owner somebody deleted
comment:3 Changed at 2008-03-21T22:37:28Z by zooko
- Milestone changed from 1.0 to undecided
comment:4 Changed at 2008-06-01T20:53:07Z by warner
- Milestone changed from eventually to undecided
comment:5 Changed at 2020-01-17T23:39:58Z by exarkun
I think this requires more design before anything happens on it. Are ad hoc modifications to filesystem state the right way to deliver configuration changes to Tahoe-LAFS? Current thinking is probably that configuration control should be API-based instead of filesystem-based.
Note: See
TracTickets for help on using
tickets.
yeah, eventually. I'm inclined to put this one off for a while, though.