Wouldn't it be nice if the Developer actually fixed this bug, instead of having customers opening TAC cases after each and every upgrade and servicepack-installation?
A permanent fix is fairly easy to apply
- make sure that the newly added "printeradmin user" is removed from Linux
- and apply the old user/Group id on the chrony.
- This cant be soo hardto create a script to verify this settings and change them where nessessary.
Curently tac fixes the problem by utilizing Root access to the affected node.creating a new UID for chrony, starts the daemon and this works untill next upate/Patch is done on the node.
It's is mine expectations only or is it in general really annoying how "sloppy" the bugfixes are handeled..
