Univention Bugzilla – Bug 39000
Check if insserv was called
Last modified: 2017-01-05 21:09:59 CET
An App called insserv in the postinst which changed the complete boot order and it looks like some Unviention services had been removed from the default runlevel. A test case should check it.
Please check if the described behaviour is reproducible and how to test it.
Added a test that will check a list of univention programs and the filenames of their respective startup scripts in /etc/rc2.d: packets = { 'univention-management-console-server': 'S20univention-management-console-server', 'univention-welcome-screen': 'S99univention-welcome-screen', 'univention-directory-policy': 'S20univention-directory-policy', 'univention-firewall': 'S05univention-firewall', 'univention-runit': 'S08univention-runit', 'univention-updater': 'S97univention-maintenance', 'univention-network-common': 'S98univention-network-common', 'univention-system-setup-boot': 'S93univention-system-setup-boot', 'univention-directory-notifier': 'S20univention-directory-notifier', 'univention-directory-listener': 'S50univention-directory-listener', 'univention-s4-connector': 'S97univention-s4-connector', 'univention-management-console-web-server': 'S20univention-management-console-web-server' } The test then checks each of these apps for installation, and, if they are installed, checks wether the init-script still exists with the correct name.