Summary: make db2bak.pl & db2ldif.pl user more user-friendly
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=233027
Found some more inconsistencies in the server utilities...
Thanks in advance,
--noriko
------- Additional Comments From nhosoi(a)redhat.com 2007-03-19 20:39 EST -------
Created an attachment (id=150447)
--> (
https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=150447&action=...)
cvs diff template-db2bak.in, template-db2bak.pl.in, template-db2ldif.in
Files:
ldap/admin/src/scripts/template-db2bak.in
ldap/admin/src/scripts/template-db2bak.pl.in
ldap/admin/src/scripts/template-db2ldif.in
ldap/admin/src/scripts/template-db2ldif.pl.in
Changes:
1) Found db2bak, db2bak.pl, and db2ldif do not backup/export into the dir/file
which do not start with the <server-id> string. It could cause the difficulty
to find out which server instance does the backup/exported file belongs to.
Also, to make them consistent with db2ldif.pl, added the "server id" string to
the back up dir name/exported ldif file name.
2) db2ldif[.pl] takes -M option. With the -M option, the server adds backend
name to the ldif file name. To reduce the redundancy, stopped adding the
backend name if -M is set.
3) made the ldif file name db2ldif generates consistent with the one db2ldif.pl
generates.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=233027
Summary: make db2bak.pl & db2ldif.pl user more user-friendly
Product: Fedora Directory Server
Version: 1.0.4
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: medium
Component: Command Line Utilities
AssignedTo: nhosoi(a)redhat.com
ReportedBy: nhosoi(a)redhat.com
QAContact: ohegarty(a)redhat.com
Estimated Hours: 0.0
------- Additional Comments From nhosoi(a)redhat.com 2007-03-19 18:41
EST -------
Created an attachment (id=150442)
-->
(
https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=150442&action=...)
cvs diff template-db2bak.pl.in template-db2ldif.pl.in
Files:
ldap/admin/src/scripts/template-db2bak.pl.in
ldap/admin/src/scripts/template-db2ldif.pl.in
Changes:
db2bak.pl: print out the back up directory
Back up directory: ...
db2ldif.pl: print out the exported ldif file name
Exported ldif file: ...
The ldif file name format: <server id>-[<backend>}<first suffix
value>]+-<date_time>.ldif
Description of problem:
[background info]
> > Both db2bak.pl and db2ldif.pl do not say much about where they are
> backing up
>
or exporting.
> > ./db2ldif.pl -D "cn=Directory Manager" -w <pw> -n userRoot`
> > adding new entry cn=export_2007_3_19_11_1_38, cn=export, cn=tasks,
> cn=config
> >
> > ./db2bak.pl -D 'cn=Directory Manager' -w <pw>
> > adding new entry cn=backup_2007_3_19_11_14_51, cn=backup, cn=tasks,
> cn=config
> >
> > Isn't it nicer the perl scripts prints out something like
> "exporting to
>
<fullpath>/<ldiffilename>" or "backing up to
<backup_dir>" if it's not
too noisy?
Yes, they should print something like that.
> >
> > Maybe, we'd better add "backend name" to the path as well? E.g.,
>
laputa-userRoot_2007_3_19_11_14_51.ldif.
Sure.
[Fix proposal]
db2bak.pl
=========
./db2bak.pl -D 'cn=Directory Manager' -w <pw>
Back up directory: /opt/fedora-ds/slapd-laputa/bak/2007_3_19_14_18_17
adding new entry cn=backup_2007_3_19_14_18_17, cn=backup, cn=tasks,
cn=config
db2ldif.pl
==========
1) if suffixes are given, the first rdn values are added to the ldif
file name
following the server id separated by '-'s.
./db2ldif.pl -D 'cn=Directory Manager' -w <pw> -s dc=example,dc=com -s
o=netscaperoot
Exported ldif file:
/opt/fedora-ds/slapd-laputa/ldif/laputa-example-netscaperoot-2007_3_19_14_18_7.ldif
adding new entry cn=export_2007_3_19_14_18_7, cn=export, cn=tasks,
cn=config
2) if backend instance names are given, the instance names are added
to the ldif
file name following the server id separated by '-'s.
./db2ldif.pl -D 'cn=Directory Manager' -w <pw> -n userRoot -n
netscapeRoot
Exported ldif file:
/opt/fedora-ds/slapd-laputa/ldif/laputa-userRoot-netscapeRoot-2007_3_19_14_18_14.ldif
adding new entry cn=export_2007_3_19_14_18_14, cn=export, cn=tasks,
cn=config
note: if '-a' options are given to the both utilities, the specified
path is
used for the back up dir/ldif file.
------------------------------------------------------------------------
--
Fedora-directory-devel mailing list
Fedora-directory-devel(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-directory-devel