Bug 40480 – Make S4 Connector init script check and fix connector/s4/listener/disabled

Bug 40480 - Make S4 Connector init script check and fix connector/s4/listener/disabled


Summary:	Make S4 Connector init script check and fix connector/s4/listener/disabled

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	S4 Connector
Version:	UCS 4.2
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	Samba maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2016-01-20 18:41 CET by Arvid Requate
Modified:	2020-07-03 20:51 CEST (History)
CC List:	0 users

See Also:
What kind of report is it?:	---
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):	Troubleshooting
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Arvid Requate

2016-01-20 18:41:49 CET

In Bug 40467 we had a situation where connector/s4/listener/disabled was activated by accident by the 97univention-s4-connector.inst joinscript.

The joinscript logic depends on univentionService="S4 Connector" being registered properly by the systems that actually run the S4-Connector.

Maybe we could/should improve this by adjusting the "start" phase of the univention-s4-connector init script in such a way, that it unsets this UCR variable (and crestarts the listener if a change was necessary) in case connector/s4/autostart is true.


It's way better to know that the listener module is not disable when the S4-Connector is running.

Comment 1 Ingo Steuwer

2020-07-03 20:51:28 CEST

This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.