You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure how this could be properly fixed. There is technically nothing wrong with the module itself, it's related to AppArmor restrictive/annoying behavior. Here are some ideas:
Defaults logfile_user value should be root (at least for Ubuntu).
Don't try to create or set permissions on the logfile, ntp is already able to create it (at least on Ubuntu).
Update the documentation of the logfile parameter for Ubuntu users.
The text was updated successfully, but these errors were encountered:
Describe the Bug
logfile
parameter is never working (target file is empty).Expected Behavior
Logs should be written to the
logfile
target.Steps to Reproduce
Environment
Additional Context
Manual installation of
ntp
withlogfile /var/log/ntp.log
line in the/etc/ntp.conf
works. Resulting file:However this Puppet module will change the permissions to:
Which somehow does not work:
I suspect this is related to AppArmor. Even if I cannot find any proof, it seems to work when the later is uninstalled.
Workaround:
However, this works with
/var/log/ntp.log
only. If you try/var/log/ntp/ntp.log
, AppArmor will explicitly deny the ntp daemon to access this file:I'm not sure how this could be properly fixed. There is technically nothing wrong with the module itself, it's related to AppArmor restrictive/annoying behavior. Here are some ideas:
logfile_user
value should beroot
(at least for Ubuntu).logfile
parameter for Ubuntu users.The text was updated successfully, but these errors were encountered: