Description of problem: ns-slapd has a -d option to turn on debugging. However, there is no way to activate this in the init script. I would recommend a setting such as SLAPD_DEBUG in the /etc/sysconfig/dirsrv or /etc/sysconfig/dirsrv-$instance file (since we source that already) and code such as: [ -f /etc/sysconfig/dirsrv-$instance ] && . /etc/sysconfig/dirsrv-$instance if [[ ! -z "$SLAPD_DEBUG" ]]; then DIRSRV_OPTS="-d $SLAPD_DEBUG" else DIRSRV_OPTS="" fi $exec -D $instbase/slapd-$instance $DIRSRV_OPTS -i $pidfile -w $startpidfile Version-Release number of selected component (if applicable): 389-ds-base-1.2.11.15-48.el6_6.x86_64 How reproducible: Always Steps to Reproduce: 1. Set "SLAPD_DEBUG=1" in /etc/sysconfig/dirsrv-$instance 2. service dirsrv restart 3. ps -ef | grep slapd Actual results: No -d option on command line of ns-slapd. Expected results: -d option and argument on command line of ns-slapd. Additional info:
Metadata Update from @nhosoi: - Issue set to the milestone: 1.3.6.0
I don't think this is a big issue for us as the development team. We can modify this by hand, or we can alter the log level in dse.ldif. I'm open to discussion, but I err to the fact this may not be widely used.
Metadata Update from @firstyear: - Custom field reviewstatus adjusted to review - Custom field version adjusted to 1.3.6 - Issue close_status updated to: None
Metadata Update from @firstyear: - Custom field reviewstatus reset
Metadata Update from @firstyear: - Custom field reviewstatus adjusted to new - Issue tagged with: Easyfix
Metadata Update from @mreynolds: - Custom field reviewstatus reset (from new) - Issue set to the milestone: 1.4 backlog (was: 1.3.6.0)
Metadata Update from @firstyear: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/1821
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.