Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Init script has no support for debug options #1821

Closed
389-ds-bot opened this issue Sep 13, 2020 · 7 comments
Closed

Init script has no support for debug options #1821

389-ds-bot opened this issue Sep 13, 2020 · 7 comments
Labels
closed: won't fix Migration flag - Issue easy fix Fix is easy
Milestone

Comments

@389-ds-bot
Copy link

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/48761


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:
@389-ds-bot 389-ds-bot added closed: won't fix Migration flag - Issue easy fix Fix is easy labels Sep 13, 2020
@389-ds-bot 389-ds-bot added this to the 1.4 backlog milestone Sep 13, 2020
@389-ds-bot
Copy link
Author

Comment from nhosoi (@nhosoi) at 2017-02-11 23:10:20

Metadata Update from @nhosoi:

  • Issue set to the milestone: 1.3.6.0

@389-ds-bot
Copy link
Author

Comment from firstyear (@Firstyear) at 2017-02-13 04:17:47

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.

@389-ds-bot
Copy link
Author

Comment from firstyear (@Firstyear) at 2017-02-13 04:17:56

Metadata Update from @Firstyear:

  • Custom field reviewstatus adjusted to review
  • Custom field version adjusted to 1.3.6
  • Issue close_status updated to: None

@389-ds-bot
Copy link
Author

Comment from firstyear (@Firstyear) at 2017-02-15 00:42:37

Metadata Update from @Firstyear:

  • Custom field reviewstatus reset

@389-ds-bot
Copy link
Author

Comment from firstyear (@Firstyear) at 2017-04-04 04:52:43

Metadata Update from @Firstyear:

  • Custom field reviewstatus adjusted to new
  • Issue tagged with: Easyfix

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2017-05-08 22:33:36

Metadata Update from @mreynolds389:

  • Custom field reviewstatus reset (from new)
  • Issue set to the milestone: 1.4 backlog (was: 1.3.6.0)

@389-ds-bot
Copy link
Author

Comment from firstyear (@Firstyear) at 2017-07-11 01:42:16

Metadata Update from @Firstyear:

  • Issue close_status updated to: wontfix
  • Issue status updated to: Closed (was: Open)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed: won't fix Migration flag - Issue easy fix Fix is easy
Projects
None yet
Development

No branches or pull requests

1 participant