-
David Zeuthen authored
- don't abort/malfunction if the /etc/PolicyKit/PolicyKit.conf configuration file is malformed; simply just continue as normal but return 'no' to every question asked. Also use syslog(3) to report this to the system log - if a .policy file is malformed, simply skip it and still include other well-formed .policy files. Use syslog(3) to report if indeed a .policy file is malformed. - drop /var/lib/PolicyKit/reload and rely on inotify to detect changes to - /etc/PolicyKit/PolicyKit.conf - Policy files in /usr/share/PolicyKit/policy - privileges in /var/lib/PolicyKit and /var/run/PolicyKit As a result, changes made to /etc/PolicyKit/PolicyKit.conf (typically an admin edits this file) and .policy files (typically these can change on package upgrades) in /usr/share/PolicyKit/policy are instantly picked up.
07b101ec