Age | Commit message (Collapse) | Author |
|
Change-Id: Ibf68b5b4d7377ea5863315ffd5b6ed24c2874961
|
|
Stale data just tastes bad, y'know?
Change-Id: I027250bfb6831ef473088e2ee2652df2a8f894a4
|
|
For whatever reason, it complains if you don't provide this. It will
then set O_NONBLOCK by itself, so I'm not really sure what the point is.
Change-Id: Iec21e48f027a9782625f5fbbe539a8a7ccc04e2c
|
|
to the httpd service
This ensures they can be restarted together correctly, as well as
ensuring the service has a socket available at all times.
Change-Id: Ifa06e217cc2209aea4bcf28ed054d74cbc091a99
|
|
It turns out the strange behaviour we were observing was due to
createHome applying an overly-restrictive mode to the public-inbox
top-level directory. This prevented public-inbox-httpd from accessing
any of the inboxes, despite it having the correct group assigned.
This fixes:
- Inbox descriptions showing up as "($INBOX_DIR/description missing)"
- Inbox pages only containing the text "No messages, yet"
- Mysterious "fatal: not a git repository: '/path/to/inbox'" errors
- Probably even more things that I simply didn't notice
Change-Id: Ia5a3d57546efd2d0375528fa10e4e979d155b045
|
|
Co-authored-by: edef <edef@unfathomable.blue>
Change-Id: I36d2c4cca542ed91630b1b832f3c7a7b97b33c65
|