Univention Bugzilla – Bug 48717
Log events to Admin Diary
Last modified: 2019-03-12 13:41:01 CET
1. Every UDM object creation 2. Every UDM object modification 3. Every UDM object move 4. Every UDM object removal 5. Join: Start and end 6. Failed join scripts 7. univention-upgrade: Start and end 8. Poweroff / Reboot
(In reply to Dirk Wiesenthal from comment #0) > 1. Every UDM object creation > 2. Every UDM object modification So we will log every cn=temporary object? "Great!" Please have a look at file:/var/lib/univention-ldap/notify/transaction and please implement some sane filtering... at least some "triggered by direct user interaction" and not subsequently triggered by a chain of internal sub-actions.) > 3. Every UDM object move > 4. Every UDM object removal > 5. Join: Start and end > 6. Failed join scripts > 7. univention-upgrade: Start and end > 8. Poweroff / Reboot
> So we will log every cn=temporary object? "Great!" No, we are not that stupid. Thanks for the feedback.
Implemented everything but 8. Poweroff / Reboot I had problems with adding a script that runs before the system halts but rsync is still available for a as long as sending the data takes.
UDM_GENERIC_* and APP_UPGRADE_* and APP_REMOVE_* events in univention-admin-diary 1.0.0-29A~4.4.0.201902261420
Created attachment 9884 [details] dont_log_empty_mods.patch As discussed, I would propose to avoid logging empty modifications, which occurr from the S4-Connector for every created user.
Done in univention-directory-manager-modules 14.0.9-2A~4.4.0.201903042337
Ok, works. The Admin Diary currently cannot correlate reflected S4-Connector changes, so they show up as unrelated changes by some cn=admin. To handle that in a better way would require changes far beyond the scope of the current project. 7e945274e9 | UCS 4.4 changelog entry
UCS 4.4 has been released: https://docs.software-univention.de/release-notes-4.4-0-en.html https://docs.software-univention.de/release-notes-4.4-0-de.html If this error occurs again, please use "Clone This Bug".