Modify ↓
#4531 closed defect (fixed)
relative paths don't work when tracd is daemonized
| Reported by: | anonymous | Owned by: | Matthew Good |
|---|---|---|---|
| Priority: | normal | Milestone: | 0.10.4 |
| Component: | web frontend/tracd | Version: | 0.10.3 |
| Severity: | minor | Keywords: | tracd |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
Tracd works erratically when daemonized if the directory parameter ( -e option ) is a relative path.
This is the intended behaviour, by looking at the code, but documentation should explicitly mention that relative paths do not work when tracd is daemonized.
Attachments (0)
Change History (6)
comment:1 by , 17 years ago
| Keywords: | documentation removed |
|---|---|
| Milestone: | → 0.10.4 |
| Owner: | changed from to |
| Status: | new → assigned |
| Summary: | tracd fails when daemonized → relative paths don't work when tracd is daemonized |
comment:3 by , 17 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
This is still a problem with —basic-auth arguments, if the path to htpasswd is relative.
comment:4 by , 17 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
follow-up: 6 comment:5 by , 17 years ago
comment:6 by , 17 years ago
Replying to mgood:
… when using
--daemonizewith--autoreload.
Does that even make sense? If not, I'd suggest to make them mutually exclusive, so they're not mixed by accident.
Note:
See TracTickets
for help on using tickets.
Yes, the problem comes from the daemonizing process changing the working directory to the root directory. However, I think we can translate the path options to absolute paths before daemonizing to avoid this altogether.