Opened 13 years ago
Closed 13 years ago
#2877 closed Enhancement (fixed)
Don't let the daemon launch if settings.json is corrupt
Reported by: | charles | Owned by: | charles |
---|---|---|---|
Priority: | Normal | Milestone: | 1.90 |
Component: | Daemon | Version: | 1.83 |
Severity: | Normal | Keywords: | |
Cc: |
Description
The daemon's behavior in 1.7x and 1.8x is to silently fall back to the default settings when hitting a corrupt settings.json file. This was well-intentioned but seems to cause more harm than good, generating quite a few user questions along the lines of "transmission isn't using my settings, no matter how many times I edit the file" etc.
Instead, transmission-daemon should say where in settings.json the parse error occurred, and then exit so that the problem can be resolved.
Change History (4)
comment:1 Changed 13 years ago by charles
- Resolution set to fixed
- Status changed from new to closed
comment:2 Changed 13 years ago by charles
- Resolution fixed deleted
- Status changed from closed to reopened
reopening for attribution
comment:3 Changed 13 years ago by charles
- Owner set to charles
- Status changed from reopened to new
comment:4 Changed 13 years ago by charles
- Resolution set to fixed
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
Fixed in trunk for 1.90 by r10135