Bug 35165 – add switch (-P) to initialize handlers only, but not start from scratch (which is what -i does)

Bug 35165 - add switch (-P) to initialize handlers only, but not start from scratch (which is what -i does)


Summary:	add switch (-P) to initialize handlers only, but not start from scratch (whic...

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Listener (univention-directory-listener)
Version:	UCS 3.2
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:	40514
	Show dependency tree / graph

Reported:	2014-06-19 11:19 CEST by Felix Botner
Modified:	2019-01-03 07:07 CET (History)
CC List:	1 user (show)

See Also:	43046
What kind of report is it?:	Feature Request
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?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Flags:	hahn: Patch_Available+

Attachments
initialize_only_but_not_from_scratch.patch (862 bytes, patch) 2014-06-19 11:20 CEST, Felix Botner	Details \| Diff
View All 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 Felix Botner

2014-06-19 11:19:47 CEST

We need a switch (-P) to run the listener in "initialize handlers only" mode, but not start from scratch (do not remove cache, handler state files etc.)

Comment 1 Felix Botner

2014-06-19 11:20:13 CEST

Created attachment 5964 [details]
initialize_only_but_not_from_scratch.patch

Comment 2 Stefan Gohmann

2017-06-16 20:40:37 CEST

This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.

Comment 3 Florian Best

2017-06-28 14:52:46 CEST

There is a Customer ID set so I set the flag "Enterprise Customer affected".

Comment 4 Stefan Gohmann

2019-01-03 07:07:46 CET

This issue has been filled against UCS 3.2. The maintenance with bug and security fixes for UCS 3.2 has ended on 30st of November 2016.

Customers still on UCS 3.2 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

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