Opened 3 years ago
Closed 2 years ago
#1974 closed defect (no response)
directory sbin/eepsite/logs not writeable
| Reported by: | Eche|on | Owned by: | zzz |
|---|---|---|---|
| Priority: | major | Milestone: | 0.9.30 |
| Component: | package/debian | Version: | 0.9.29 |
| Keywords: | Cc: | ||
| Parent Tickets: | Sensitive: | no |
Description
Hi!
I copied over the skeleton jetty.xml to my eepsite directory.
And the line <Set name="filename">./eepsite/logs/yyyy_mm_dd.request.log</Set>
did not work as expected, as i2p tryed to log in /usr/sbin/… and was not allowed to.
I replaced the ./eepsite with the real path, now no error appears.
Subtickets
Change History (2)
comment:1 Changed 3 years ago by
| Status: | new → infoneeded_new |
|---|
comment:2 Changed 2 years ago by
| Resolution: | → no response |
|---|---|
| Status: | infoneeded_new → closed |
Note: See
TracTickets for help on using
tickets.
Yeah, in the router startup code, where we migrate the jetty.xml files from $I2P to the config directory, we replace the ./eepsite paths with a full absolute path.
That doesn't happen if you copy it over manually.
Do we need to put some instructions somewhere to do that?