5:29 p.m.
Hello, fedora-directory-users list;
We are working on the setup and clean-up code in the next version:
(please see also
http://directory.fedoraproject.org/wiki/New_Setup_Design). I'd like to
have your thoughts on the behavior when you run "rpm -e fedora-ds". The
previous version cleaned up all the binaries and instances but the
certificate and key dbs.
# ls alias
secmod.db slapd-ID-key3.db slapd-ID-cert8.db
Do we want to leave them untouched on the next version, as well? How
about other files such as ldif files or backup files? Or do we want to
remove all the fedora-ds related files?
Your input would be greatly appreciated.
--noriko
6:47 a.m.
On Tue, 2007-07-17 at 15:29 -0700, Noriko Hosoi wrote:
Hello, fedora-directory-users list;
We are working on the setup and clean-up code in the next version:
(please see also
http://directory.fedoraproject.org/wiki/New_Setup_Design). I'd like to
have your thoughts on the behavior when you run "rpm -e fedora-ds". The
previous version cleaned up all the binaries and instances but the
certificate and key dbs.
# ls alias
secmod.db slapd-ID-key3.db slapd-ID-cert8.db
Do we want to leave them untouched on the next version, as well? How
about other files such as ldif files or backup files? Or do we want to
remove all the fedora-ds related files?
Your input would be greatly appreciated.
--noriko
Personally, I prefer "rpm -e" to remove only the files that were
originally installed by the package.
-Steve
9:02 a.m.
On Wed, 18 Jul 2007, Steve Rigler wrote:
Personally, I prefer "rpm -e" to remove only the files that
were
originally installed by the package.
I'll second that.
Chris St. Pierre
Unix Systems Administrator
Nebraska Wesleyan University
----------------------------
LOPSA Sysadmin Days: Professional Training for Professional SysAdmins
August 6-7, Cherry Hill, NJ
http://lopsa.org/SysadminDays
9:49 a.m.
Chris St. Pierre wrote:
On Wed, 18 Jul 2007, Steve Rigler wrote:
> Personally, I prefer "rpm -e" to remove only the files that were
> originally installed by the package.
I'll second that.
Ok. The way Fedora DS works with respect to RPM install is a
little
different than OpenLDAP or other similar server software packages. With
those, you generally get some of the configuration for your "instance"
with the RPM package (there is usually only the one instance, and if you
want to run another server, you have to manually configure it
yourself). With Fedora DS, there are no instance specific
files/directories in the RPM. You have to run the setup command to
create these, and this will create the following directories:
/etc/fedora-ds/slapd-instance - contains dse.ldif and key and cert
databases, pin.txt file, maybe the keytab as well
/usr/lib64/fedora-ds/slapd-instance - scripts like db2ldif, ldif2db, etc.
/var/lib/fedora-ds/slapd-instance - databases
/var/log/fedora-ds/slapd-instance - logs
/var/tmp/fedora-ds/slapd-instance - tmp files
/var/lock/fedora-ds/slapd-instance - lock files/dirs
So if you rpm -e, all of these will be left behind. I don't know if
that is expected or desired.
Chris St. Pierre
Unix Systems Administrator
Nebraska Wesleyan University
----------------------------
LOPSA Sysadmin Days: Professional Training for Professional SysAdmins
August 6-7, Cherry Hill, NJ
http://lopsa.org/SysadminDays
--
Fedora-directory-users mailing list
Fedora-directory-users(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-directory-users
10:04 a.m.
On Wed, 2007-07-18 at 08:49 -0600, Richard Megginson wrote:
Chris St. Pierre wrote:
> On Wed, 18 Jul 2007, Steve Rigler wrote:
>
>> Personally, I prefer "rpm -e" to remove only the files that were
>> originally installed by the package.
>
> I'll second that.
Ok. The way Fedora DS works with respect to RPM install is a little
different than OpenLDAP or other similar server software packages. With
those, you generally get some of the configuration for your "instance"
with the RPM package (there is usually only the one instance, and if you
want to run another server, you have to manually configure it
yourself). With Fedora DS, there are no instance specific
files/directories in the RPM. You have to run the setup command to
create these, and this will create the following directories:
/etc/fedora-ds/slapd-instance - contains dse.ldif and key and cert
databases, pin.txt file, maybe the keytab as well
/usr/lib64/fedora-ds/slapd-instance - scripts like db2ldif, ldif2db, etc.
/var/lib/fedora-ds/slapd-instance - databases
/var/log/fedora-ds/slapd-instance - logs
/var/tmp/fedora-ds/slapd-instance - tmp files
/var/lock/fedora-ds/slapd-instance - lock files/dirs
So if you rpm -e, all of these will be left behind. I don't know if
that is expected or desired.
That's fine for me. It's actually good because when I'm testing a new
piece of software I might reinstall it from scratch. If it leaves some
old files behind I can always go back and compare to a working install
to see where I screwed up.
-Steve
10:11 a.m.
Steve Rigler wrote:
On Wed, 2007-07-18 at 08:49 -0600, Richard Megginson wrote:
> Chris St. Pierre wrote:
>> On Wed, 18 Jul 2007, Steve Rigler wrote:
>>
>>> Personally, I prefer "rpm -e" to remove only the files that were
>>> originally installed by the package.
>> I'll second that.
> Ok. The way Fedora DS works with respect to RPM install is a little
> different than OpenLDAP or other similar server software packages. With
> those, you generally get some of the configuration for your "instance"
> with the RPM package (there is usually only the one instance, and if you
> want to run another server, you have to manually configure it
> yourself). With Fedora DS, there are no instance specific
> files/directories in the RPM. You have to run the setup command to
> create these, and this will create the following directories:
> /etc/fedora-ds/slapd-instance - contains dse.ldif and key and cert
> databases, pin.txt file, maybe the keytab as well
> /usr/lib64/fedora-ds/slapd-instance - scripts like db2ldif, ldif2db, etc.
> /var/lib/fedora-ds/slapd-instance - databases
> /var/log/fedora-ds/slapd-instance - logs
> /var/tmp/fedora-ds/slapd-instance - tmp files
> /var/lock/fedora-ds/slapd-instance - lock files/dirs
>
> So if you rpm -e, all of these will be left behind. I don't know if
> that is expected or desired.
That's fine for me. It's actually good because when I'm testing a new
piece of software I might reinstall it from scratch. If it leaves some
old files behind I can always go back and compare to a working install
to see where I screwed up.
Certs and keys are particularly important to keep around because they
may have a financial value if purchased from a CA like VeriSign.
rob
11:48 a.m.
Steve Rigler wrote:
On Wed, 2007-07-18 at 08:49 -0600, Richard Megginson wrote:
> Chris St. Pierre wrote:
>
>> On Wed, 18 Jul 2007, Steve Rigler wrote:
>>
>>
>>> Personally, I prefer "rpm -e" to remove only the files that were
>>> originally installed by the package.
>>>
>> I'll second that.
>>
> Ok. The way Fedora DS works with respect to RPM install is a little
> different than OpenLDAP or other similar server software packages. With
> those, you generally get some of the configuration for your "instance"
> with the RPM package (there is usually only the one instance, and if you
> want to run another server, you have to manually configure it
> yourself). With Fedora DS, there are no instance specific
> files/directories in the RPM. You have to run the setup command to
> create these, and this will create the following directories:
> /etc/fedora-ds/slapd-instance - contains dse.ldif and key and cert
> databases, pin.txt file, maybe the keytab as well
> /usr/lib64/fedora-ds/slapd-instance - scripts like db2ldif, ldif2db, etc.
> /var/lib/fedora-ds/slapd-instance - databases
> /var/log/fedora-ds/slapd-instance - logs
> /var/tmp/fedora-ds/slapd-instance - tmp files
> /var/lock/fedora-ds/slapd-instance - lock files/dirs
>
> So if you rpm -e, all of these will be left behind. I don't know if
> that is expected or desired.
>
That's fine for me. It's actually good because when I'm testing a new
piece of software I might reinstall it from scratch. If it leaves some
old files behind I can always go back and compare to a working install
to see where I screwed up.
-Steve
If "rpm -e fedora-ds" leaves all the directories listed above, the
following "rpm -i fedora-ds" + setup operation would be the in-place
upgrade instead of the fresh install if the same server ID (slapd-ID) is
chosen. Maybe, that'd be the expected behavior for many
administrators. For others, we could have one more question in the
setup/upgrade dialog if the setup is a fresh install (wipe out the old
files) or a in-place upgrade (use the old files). If the answer is
"fresh install", we can clean up the old files, then.
Another thing is if the host is no longer used for the Fedora Directory
Server, you may want to clean up the disk eventually. At that time,
there is no tool to remove them. Theoretically, all the
files/directories are under fedora-ds somewhere, so it won't be
difficult to remove them manually, though. But it looks a little lame...
Thank you for your feedbacks.
--noriko
10:16 a.m.
On Wed, 18 Jul 2007, Noriko Hosoi wrote:
If "rpm -e fedora-ds" leaves all the directories listed
above, the following
"rpm -i fedora-ds" + setup operation would be the in-place upgrade instead of
the fresh install if the same server ID (slapd-ID) is chosen. Maybe, that'd
be the expected behavior for many administrators. For others, we could have
one more question in the setup/upgrade dialog if the setup is a fresh install
(wipe out the old files) or a in-place upgrade (use the old files). If the
answer is "fresh install", we can clean up the old files, then.
Another thing is if the host is no longer used for the Fedora Directory
Server, you may want to clean up the disk eventually. At that time, there is
no tool to remove them. Theoretically, all the files/directories are under
fedora-ds somewhere, so it won't be difficult to remove them manually, though.
But it looks a little lame...
If 'setup' creates all of that stuff, could there be an 'unsetup'
command that removes it all? I.e., if installation is:
rpm -hvU fedora-ds-....
/path/to/setup
Then uninstallation could be:
/path/to/unsetup
rpm -e fedora-ds
That way removal of all of the other stuff could be at the option of
the administrator.
Just a thought. I'm sure you have nothing better to do than write
scripts consisting of a few hundred lines of rm. :)
Chris St. Pierre
Unix Systems Administrator
Nebraska Wesleyan University
----------------------------
LOPSA Sysadmin Days: Professional Training for Professional SysAdmins
August 6-7, Cherry Hill, NJ
http://lopsa.org/SysadminDays
10:12 a.m.
Chris St. Pierre wrote:
On Wed, 18 Jul 2007, Noriko Hosoi wrote:
> If "rpm -e fedora-ds" leaves all the directories listed above, the
> following "rpm -i fedora-ds" + setup operation would be the in-place
> upgrade instead of the fresh install if the same server ID (slapd-ID)
> is chosen. Maybe, that'd be the expected behavior for many
> administrators. For others, we could have one more question in the
> setup/upgrade dialog if the setup is a fresh install (wipe out the
> old files) or a in-place upgrade (use the old files). If the answer
> is "fresh install", we can clean up the old files, then.
>
> Another thing is if the host is no longer used for the Fedora
> Directory Server, you may want to clean up the disk eventually. At
> that time, there is no tool to remove them. Theoretically, all the
> files/directories are under fedora-ds somewhere, so it won't be
> difficult to remove them manually, though. But it looks a little lame...
If 'setup' creates all of that stuff, could there be an 'unsetup'
command that removes it all? I.e., if installation is:
rpm -hvU fedora-ds-....
/path/to/setup
Then uninstallation could be:
/path/to/unsetup
rpm -e fedora-ds
That way removal of all of the other stuff could be at the option of
the administrator.
Just a thought. I'm sure you have nothing better to do than write
scripts consisting of a few hundred lines of rm. :)
find / -name fedora-ds -exec rm
-rf {} \;
:-)
Chris St. Pierre
Unix Systems Administrator
Nebraska Wesleyan University
----------------------------
LOPSA Sysadmin Days: Professional Training for Professional SysAdmins
August 6-7, Cherry Hill, NJ
http://lopsa.org/SysadminDays
--
Fedora-directory-users mailing list
Fedora-directory-users(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-directory-users
6119
days inactive
6121
days old
389-users@lists.fedoraproject.org
8 comments
5 participants
participants (5)
-
Chris St. Pierre -
Noriko Hosoi -
Rich Megginson -
Rob Crittenden -
Steve Rigler