Bug 1275763 - [RFE] add setup-ds.pl option to disable instance specific scripts
[RFE] add setup-ds.pl option to disable instance specific scripts
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Noriko Hosoi
Viktor Ashirov
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2015-10-27 12:37 EDT by Noriko Hosoi
Modified: 2016-11-03 16:36 EDT (History)
3 users (show)

See Also:
Fixed In Version: 389-ds-base-
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-11-03 16:36:53 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Noriko Hosoi 2015-10-27 12:37:08 EDT
This bug is created as a clone of upstream ticket:

Now that https://fedorahosted.org/389/ticket/528 is fixed, the next step is to allow building the server with the instance specific scripts disabled.

Add a new configure option:
AC_ARG_ENABLE(instance-scripts, AS_HELP_STRING([--enable-instance-scripts], [Enable setup to create instance specific scripts in the system lib/dirsrv directory (default: yes)])

The default is yes, so as not to break any existing builds.  If you do not want setup to create the instance specific scripts, use configure ... --disable-instance-scripts
Comment 1 Viktor Ashirov 2016-04-06 16:36:44 EDT
Per email discussion, changing this to RFE. 


Fix Description: Instead of defining a configure option, we provide a new
option in setup-ds.pl, slapd.InstScriptsEnabled?, which defaults to false. All
new installs of 389 will NOT install with a inst_dir nor the scripts that are in
that directory.
Additionally, this change fixes setup-ds.pl to correctly use the sbindir scripts
to start/stop the server instance during installation.
Finally, we add support for setup-ds.pl so that in --update if the inst_dir
exists, scripts will be updated, but if it does not exist, no action is taken.
In time, we will alter --update to *remove* the scripts within inst_dir during
the update (We have no way of knowing if a customer has put custom scripts in
/opt/dirsrv/sbin/setup-ds.pl slapd.InstScriptsEnabled?=false
Comment 2 Viktor Ashirov 2016-04-07 12:57:46 EDT
Doc bug: https://bugzilla.redhat.com/show_bug.cgi?id=1324907

And by default old behaviour will be kept, i.e. scripts will be installed.
Comment 4 Amita Sharma 2016-09-14 06:11:21 EDT
A minor bug - https://bugzilla.redhat.com/show_bug.cgi?id=1348903
Rest worked as expected.
Comment 6 errata-xmlrpc 2016-11-03 16:36:53 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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