#49075 Utility command had better use INFO log level for the output?
Closed: wontfix 4 years ago Opened 4 years ago by nhosoi.

This is an example. The dbverify utility uses the ERR level for the verbose mode output. The word "ERR" may not be appropriate.

dbverify -V

[02/Jan/2017:17:24:14.120315218 -0800] - ERR - dbverify_ext - /var/lib/dirsrv/slapd-test/db/userRoot/mail.db: ok
[02/Jan/2017:17:24:14.233058862 -0800] - ERR - dbverify_ext - /var/lib/dirsrv/slapd-test/db/userRoot/telephoneNumber.db: ok
[02/Jan/2017:17:24:14.286457810 -0800] - ERR - dbverify_ext - /var/lib/dirsrv/slapd-test/db/userRoot/cn.db: ok
....
[02/Jan/2017:17:24:15.154115725 -0800] - ERR - dbverify_ext - /var/lib/dirsrv/slapd-test/db/NetscapeRoot/aci.db: ok
DB verify: Passed


I agree, and it looks like other tasks also use ERR instead of INFO. This was such a large refactoring job that some of these slipped through the cracks.

360d797..9fc1027 master -> master
commit 9fc1027
Author: Mark Reynolds mreynolds@redhat.com
Date: Wed Jan 4 16:54:20 2017 -0500

Metadata Update from @nhosoi:
- Issue assigned to mreynolds
- Issue set to the milestone: 1.3.6 backlog

4 years ago

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to review (was: ack)
- Issue status updated to: Open (was: Closed)

4 years ago

Ack, these messages are fine.

One day we have to agree on a column width ;)

Metadata Update from @firstyear:
- Custom field reviewstatus adjusted to ack (was: review)

4 years ago

Ack, these messages are fine.
One day we have to agree on a column width ;)

Even on my 1080p widescreen monitor the logging is still out of scope. So yes, I adjust lines so they fit in my monitor/IDE

Screenshot_from_2017-05-04_09-55-51.png

46011e2..0762e39 master -> master

d518a45..2ae1521 389-ds-base-1.3.6 -> 389-ds-base-1.3.6

Metadata Update from @mreynolds:
- Issue close_status updated to: fixed
- Issue set to the milestone: 1.3.6.0 (was: 1.3.6 backlog)
- Issue status updated to: Closed (was: Open)

4 years ago

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/2134

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: fixed)

a year ago

Login to comment on this ticket.

Metadata