#2493 Check chown_debug_file() usage
Closed: Fixed None Opened 4 years ago by sbose.

Currently chown_debug_file() is called unconditionally and it does not make any check if debug to files is active or not. This might cause irritating error messages e.g. when journald is used.


Fields changed

rhbz: => 0

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.12.4

Moving tickets that didn't make the 1.12.4 release to 1.12.5

milestone: SSSD 1.12.4 => SSSD 1.12.5

Fields changed

milestone: SSSD 1.12.5 => SSSD 1.13.2
owner: jhrozek => pcech
sensitive: => 0

Fields changed

patch: 0 => 1

Fields changed

status: new => assigned

To reproduce this you should start sssd without the '-f' option and /var/log/sssd should either empty or not exist. If you then check the journal you you see something like

# journalctl -r | grep 'chown failed'
Okt 23 13:54:57 sssd-devel.sssd.devel sssd_ifp[4963]: chown failed for [sssd_ifp]: [2]
Okt 23 13:54:57 sssd-devel.sssd.devel sssd_pam[4962]: chown failed for [sssd_pam]: [2]
Okt 23 13:54:57 sssd-devel.sssd.devel sssd_nss[4961]: chown failed for [sssd_nss]: [2]
Okt 23 13:54:57 sssd-devel.sssd.devel sssd_be[4960]: chown failed for [sssd_ad.devel]: [2]
Okt 23 13:54:57 sssd-devel.sssd.devel sssd_be[4960]: chown failed for [sssd_ad.devel]: [2]

Fields changed

resolution: => fixed
status: assigned => closed

Metadata Update from @sbose:
- Issue assigned to pcech
- Issue set to the milestone: SSSD 1.13.2

2 years ago

Login to comment on this ticket.

Metadata