Merge lp:~cjwatson/charms/precise/squid-forwardproxy/umask into lp:~canonical-launchpad-branches/charms/precise/squid-forwardproxy/trunk
Proposed by
Colin Watson
Status: | Merged |
---|---|
Merged at revision: | 38 |
Proposed branch: | lp:~cjwatson/charms/precise/squid-forwardproxy/umask |
Merge into: | lp:~canonical-launchpad-branches/charms/precise/squid-forwardproxy/trunk |
Diff against target: |
24 lines (+7/-0) 2 files modified
config.yaml (+5/-0) templates/main_config.template (+2/-0) |
To merge this branch: | bzr merge lp:~cjwatson/charms/precise/squid-forwardproxy/umask |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Colin Watson (community) | Approve | ||
Review via email: mp+299135@code.launchpad.net |
Commit message
Allow specifying a umask other than squid's default of 027.
Description of the change
Allow specifying a umask other than squid's default of 027.
The default umask is reasonable in many environments, but in the case where the system's main purpose is squid and anyone who has access to the system at all ought to be able to read its logs, it just makes things unnecessarily awkward.
To post a comment you must log in.
I'm going to go ahead with this. The target branch is just used by mojo-lp-snap-proxy right now, and it's easy enough to undo if people don't like this approach.