Bug 45037

Summary:	Start AD Connector in foreground without daemonizing
Product:	UCS	Reporter:	Florian Best <best>
Component:	AD Connector	Assignee:	Florian Best <best>
Status:	CLOSED FIXED	QA Contact:	Arvid Requate <requate>
Severity:	normal
Priority:	P5	CC:	gohmann
Version:	UCS 4.2	Flags:	best: Patch_Available+
Target Milestone:	UCS 4.2-2-errata
Hardware:	Other
OS:	Linux
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):	Troubleshooting
Max CVSS v3 score:
Bug Depends on:	45001
Bug Blocks:
Attachments:	patch

Description Florian Best

2017-07-18 16:16:31 CEST

The same goes for the AD connector.

+++ This bug was initially created as a clone of Bug #45001 +++

It should be possible to start the S4 Connector in foreground without daemonizing it.
This makes it possible to debug things faster by importing PDB and set breakpoints.

The only thing which is necessary to do this is to:
uncomment the daemon() function call.
don't redirect sys.stdout to the opened file.

Comment 1 Florian Best

2017-07-18 16:47:07 CEST

Created attachment 9040 [details]
patch

Comment 2 Florian Best

2017-07-19 11:02:45 CEST

univention-ad-connector (11.0.6-10):
r81242 | Bug #45037: add possibility to start AD connector in foreground

univention-ad-connector.yaml:
NONE | YAML Bug #45011 Bug #45037

Comment 3 Arvid Requate

2017-07-25 18:32:42 CEST

Ok. I recommend fixing Bug 41335 too to avoid issues with a running Connector.

Comment 4 Arvid Requate

2017-11-01 13:49:24 CET

<http://errata.software-univention.de/ucs/4.2/205.html>