juju machine and unit agent logs should be readable by adm
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Wishlist
|
Nam Nguyen |
Bug Description
Hi,
Per convention in /var/log, e.g. syslog and kern.log, log files should be created using the adm group and allow group readable permissions. Juju creates them as follows:
| -rw------- 1 syslog syslog 64528916 May 11 18:00 machine-196.log
| -rw------- 1 syslog syslog 218392032 Jun 12 23:59 unit-ntp-24.log
| -rw------- 1 syslog syslog 165752634 Jun 13 00:02 unit-landscape-
I think they should be:
| -rw-r----- 1 syslog adm 64528916 May 11 18:00 machine-196.log
| -rw-r----- 1 syslog adm 218392032 Jun 12 23:59 unit-ntp-24.log
| -rw-r----- 1 syslog adm 165752634 Jun 13 00:02 unit-landscape-
Example of other logs in /var/log:
| -rw-r----- 1 syslog adm 1658178 Jun 13 00:02 /var/log/auth.log
| -rw-r----- 1 syslog adm 2051 May 22 02:01 /var/log/kern.log.1
| -rw-r----- 1 syslog adm 581 Jun 9 06:47 /var/log/mail.log
| -rw-r----- 1 syslog adm 792829546 Jun 13 00:04 /var/log/syslog
This is really a wishlist item that reduces sysadmin frustration having to sudo to access juju agent logs.
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
tags: | added: bitesize logging |
Changed in juju: | |
milestone: | none → 2.7-beta1 |
status: | Triaged → Fix Committed |
Changed in juju: | |
status: | Fix Committed → In Progress |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
pr: https:/ /github. com/juju/ juju/pull/ 10696