Bug 41925 – PDF-Printserver-Joinscript should not recreate the share object if it is moved

Bug 41925 - PDF-Printserver-Joinscript should not recreate the share object if it is moved


Summary:	PDF-Printserver-Joinscript should not recreate the share object if it is moved

Status:	REOPENED

Product:	UCS
Classification:	Unclassified
Component:	Printserver
Version:	UCS 4.4
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2016-08-08 11:44 CEST by Stefan
Modified:	2020-07-03 23:45 CEST (History)
CC List:	2 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	2: Improvement: Would be a product improvement
Who will be affected by this bug?:	1: Will affect a very few installed domains
How will those affected feel about the bug?:	1: Nuisance – not a big deal but noticeable
User Pain:	0.011
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):	External feedback
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 Stefan 2016-08-08 11:44:41 CEST

The PDF-Printserver-Joinscript creates a share object in cn=shares,$BASEDN. It don't check if it already exist in other position. So if the share object is moved and the server is rejoined it creates a new object, so at the end there are two objects. So the check should be extended so that the script recognizes also the moved object and so don't create a new object in this case.

Comment 1 Ingo Steuwer

2020-07-03 20:52:06 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.