Bug 53337 - ADC still uses SysV init script instead of systemd
ADC still uses SysV init script instead of systemd
Status: NEW
Product: UCS
Classification: Unclassified
Component: AD Connector
UCS 5.0
Other Linux
: P5 normal (vote)
: ---
Assigned To: Samba maintainers
Samba maintainers
: systemd
Depends on:
Blocks: 43691
  Show dependency treegraph
 
Reported: 2021-05-27 10:48 CEST by Philipp Hahn
Modified: 2021-05-27 10:53 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Development Internal
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philipp Hahn univentionstaff 2021-05-27 10:48:30 CEST
For UCS-5 we switched most services to systemd, but ADC still uses /etc/init.d/univention-ad-connector

services/univention-ad-connector/debian/univention-ad-connector.init
services/univention-ad-connector/scripts/prepare-new-instance
docs/extended-docs/windows-5.0.xml:127
Comment 1 Florian Best univentionstaff 2021-05-27 10:53:20 CEST
(In reply to Philipp Hahn from comment #0)
> For UCS-5 we switched most services to systemd
Not really true. We switched:
univention-directory-listener, univention-directory-notifier, univention-dhcp, univention-network-manager, univention-system-setup.
Missing is still:
univention-docker-container-mode, 
univention-directory-policy
univention-management-console-server
univention-management-console-web-server
univention-demo-configuration
univention-ad-connector
univention-cloud-init
univention-s4-connector
debian/univention-saml
univention-updater.univention-maintenance
univention-firewall