Univention Bugzilla – Bug 41788
Upstart scripts are not started
Last modified: 2016-11-09 10:38:44 CET
Our upstart scripts are currently not started, maybe we have to convert them to systemd scripts
https://wiki.ubuntu.com/SystemdForUpstartUsers
upstart/ucc-ntpdate.conf - deleted timesyncd is now the default timesync tool * ucc-image-toolkit - removed dependency to ntpdate * univention-corporate-client - removed dependency to ntpdate - added template for etc/systemd/timesyncd.conf to set ucc/timeserver as ntp server for timesyncd
removed univention-upstart
univention-corporate-client removed: * conffiles/etc/init/lightdm.conf * conffiles/etc/init/plymouth-stop.conf * upstart/ucc-update.conf -> systemd ucc-update.service (after network, blocks lightdm) * upstart/ucc-base.conf,ucc-syspol.conf,ucc-syspol-timeout.conf -> ucc-syspol replaced by univention-ucc-fetch-system-policies call in initram (and during join) -> ucc-base and ucc-syspol replaced by new univention-ucc-initramfs/scripts/update-base-config (also called in initram) added: * ucc-syslog.service (restart syslog after network is up) - without this the client wasn't able to remote syslog
univention-ucc-pam removed upstart ucc-nss.conf added debian/ucc-nss-update.service systemd service (start /usr/sbin/univention-ucc-update-nss after network is up)
OK: Removal of upstart scripts OK: 3 new systemd service scripts: ucc-update ucc-syslog ucc-nss-update. OK: changelog Verified
UCC 3.0 has been released. If this bug occurs again, please clone this bug.