Description of problem: db2bak.pl man page should be improved. How reproducible: Always Steps to Reproduce: man db2bak.pl, options -a and -A should be clearly described with example. Please see https://bugzilla.redhat.com/show_bug.cgi?id=1044202#c3 for more details.
I don't understand. When you use -A backupdir, does it create a timestamp subdirectory of backupdir and use that for the backup?
Replying to [comment:7 rmeggins]:
Right. Could you give me a good English sentence for that? This is the existing "-a backupdir": {{{ -a backupdir The directory where the backup should be stored. }}} Thanks!!
Ok. Maybe something like this: -A backupdir - This is similar to -a, except that a sub-directory of backupdir will be created for the backup, and the name of the sub-directory will be a timestamp of the form ....whatever the form is....
Thank you, Rich! Does this look good? Please note that "-a" is bold; "backupdir" and "server-instance-date_time" are underlined. {{{ -A backupdir This is similar to -a, except that a sub-directory of backupdir will be created for the backup, and the name of the sub-direcā tory will be a timestamp of the form server-instance-date_time. }}}
git patch file (master) -- fixed the description of "-A" based on the suggestion by Rich (Thanks!!) 0001-Ticket-48008-db2bak.pl-man-page-should-be-improved.patch
Thank you for your help, Rich!!
Pushed to master: 37eca99..bb55a72 master -> master commit bb55a72
Metadata Update from @rmeggins: - Issue assigned to nhosoi - Issue set to the milestone: 1.3.4.0
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/1339
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.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)
Login to comment on this ticket.