Bug 32205 – Removing files from SYSVOL share is hard

Bug 32205 - Removing files from SYSVOL share is hard


Summary:	Removing files from SYSVOL share is hard

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Samba4
Version:	UCS 4.2
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:	35469
	Show dependency tree / graph

Reported:	2013-08-09 09:16 CEST by Sönke Schwardt-Krummrich
Modified:	2020-07-03 20:54 CEST (History)
CC List:	3 users (show)

See Also:	27483 49952
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?:	2: Will only affect a few installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.046
Enterprise Customer affected?:	Yes
School Customer affected?:	Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2014072421000172 2015080621000363
Bug group (optional):
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 Sönke Schwardt-Krummrich

2013-08-09 09:16:06 CEST

If a customer has distributed a custom script/file via SYSVOL share, it is not that easy to remove that file later on due to the SYSVOL replication. The file has to be removed (nearly) simultaneously from all S4 systems to prevent that the file is redistributed during the next run of the sysvol-sync-cronjob.

Is there an easier way for deleting files on all SYSVOL shares? If not, there should be an easier way :-)

Comment 1 Arvid Requate

2013-08-09 10:09:12 CEST

The samba example rsync script uses --delete-after, maybe we can do something similar.

Comment 2 Janis Meybohm

2014-07-25 10:31:08 CEST

Ticket#: 2014072421000172

This limitation also applies to the netlogon share.

Comment 3 Michael Grandjean

2015-08-07 12:34:49 CEST

2015080621000363

Comment 4 Ingo Steuwer

2020-07-03 20:54:29 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.