389-devel September 2009

389-devel@lists.fedoraproject.org

5 participants
37 discussions

Please review: Bug 520483 - setup-ds-admin.pl: Can't call method "getErrorString" on an undefined value at /usr/lib64/dirsrv/perl/AdminUtil.pm line 405.
by Rich Megginson 21 Sep '09

21 Sep '09

https://bugzilla.redhat.com/show_bug.cgi?id=520483 Resolves: bug 520483 Bug Description: setup-ds-admin.pl: Can't call method "getErrorString" on an undefined value at /usr/lib64/dirsrv/perl/AdminUtil.pm line 405. Reviewed by: ??? Files: see diff Fix Description: Just use "unknown" as the error string. Platforms tested: Fedora 11 x86_64 Flag Day: no Doc impact: no https://bugzilla.redhat.com/attachment.cgi?id=362022&action=diff

1 0

Please review: Bug 523476 - 389-ds-base/glibmm24: conflicting perl provides
by Rich Megginson 21 Sep '09

21 Sep '09

Basically just rename Util to DSUtil https://bugzilla.redhat.com/attachment.cgi?id=362019&action=diff https://bugzilla.redhat.com/attachment.cgi?id=362020&action=diff

1 1

Please review: Running setup-ds-admin.pl -u on replica with ldaps chokes on CA cert
by Rich Megginson 21 Sep '09

21 Sep '09

2 2

Re: [389-devel] Please review: Add update code - make setup-ds.pl -u do updates
by Rich Megginson 21 Sep '09

21 Sep '09

Noriko Hosoi wrote: > On 09/17/2009 04:12 PM, Rich Megginson wrote: >> >> ------------------------------------------------------------------------ >> >> -- >> 389-devel mailing list >> 389-devel(a)redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-directory-devel >> > Hi Rich, > > I noticed these 2 minor things. Other than these, your patch looks good. Thanks. Fixed and pushed to master. To ssh://git.fedorahosted.org/git/389/ds.git 2de80f5..cc89083 master -> master commit cc89083f1177606d4cbbb52f8cdc5e34d0d16f70 Author: Rich Megginson <rmeggins(a)redhat.com> Date: Wed Sep 9 17:01:49 2009 -0600 Add update code - make setup-ds.pl -u do updates > > diff --git a/ldap/admin/src/scripts/Setup.pm.in > b/ldap/admin/src/scripts/Setup.pm.in > index 7ad57c1..f314d67 100644 > --- a/ldap/admin/src/scripts/Setup.pm.in > +++ b/ldap/admin/src/scripts/Setup.pm.in > @@ -142,6 +145,7 @@ sub init { > $self->{keep} = $keep; > $self->{preonly} = $preonly; > $self->{update} = $update; > + $self->{force} = *$update;* <== could this be "$force"? > $self->{logfile} = $logfile; > $self->{log} = new SetupLog($self->{logfile}); > # if user supplied inf file, use that to initializ > > > diff --git a/ldap/admin/src/scripts/dsupdate.map.in > b/ldap/admin/src/scripts/dsupdate.map.in > new file mode 100644 > +# Copyright (C) *2007* Red Hat, Inc. <== 2009? :) > +# All rights reserved. > +# END COPYRIGHT BLOCK > > --noriko >

1 0

Please review: Add update code - make setup-ds.pl -u do updates
by Rich Megginson 21 Sep '09

21 Sep '09

2 1

A student hopes to learn more about the 389 Directory Server Community and the Free/Open Source Software
by Tiebing Shi 20 Sep '09

20 Sep '09

Dear friends, I have been reading your postings to the mailing lists of the 389 Directory Server Community. I have really enjoyed reading about your collaborative creative activities and your perspectives on the free/open source software. My name is Tiebing Shi and I am a Ph.D. student at Queen's University in Canada. I am very interested in learning more about the Free/Open Source Software Community. The study that I am doing for my Ph.D. thesis is called "User Creativity: An Investigation of the Free/Open Source Software Community." The purpose of my thesis is to study how developers and users collectively create free/open source software. I sincerely invite you to participate in my study. I would like to interview you in your role as a developer and/or user in your legendary 389 Directory Server Community. Your experiences of developing and/or using 389 Directory Server software and your perspectives on the free/open source software will greatly help me to understand the creative activities of the 389 Directory Server Community and the whole Free/Open Source Software Community. If your time permits, I would like to interview you via phone. The phone interview will last about 1 hour. If you like, we can conduct our interview via email. Please be kindly informed that there is no obligation to participate in this study. But your participation will be highly appreciated. Your confidentiality will be protected. For example, your real name will NOT be used in my thesis and future publications. Further information about this study and our interview will be provided to you upon request. Please respond to this email to let me know your interest in participating in a phone or an email interview with me. If you select the phone interview format, please select a time for an interview that is most convenient for you. Please also let me know your phone number and time zone (my time zone is Eastern Daylight Time) so that I can call you at your local time you select. Should you have any questions, please do not hesitate to contact me. I will respond to you as soon as possible. Thank you for your support and I look forward to talking with you. Sincerely, Tiebing Shi Queen's School of Business, Queen’s University Kingston, ON, Canada K7L 3N6 Tel: 613-533-2377 (Office) Email: tshi(a)business.queensu.ca

1 0

Please review: Add support for new ds base update framework
by Rich Megginson 18 Sep '09

18 Sep '09

This is for the admin server/console code

2 1

Please Review: Don't use admin-pattern macro in SELinux policy
by Nathan Kinder 17 Sep '09

17 Sep '09

2 2

Please Review: Add SELinux policy for SNMP subagent (ldap-agent)
by Nathan Kinder 17 Sep '09

17 Sep '09

2 2

Please Review: SELinux policy change for LDAPI
by Nathan Kinder 10 Sep '09

10 Sep '09

2 2

Please Review: Add selinux policy module for ns-slapd
by Nathan Kinder 09 Sep '09

09 Sep '09

3 3

Upgrade procedures
by Rich Megginson 02 Sep '09

02 Sep '09

I'm envisioning something like patch files in an RPM - things that can easily come and go depending on what needs to be done for a particular release. In this case, instead of patch files, these would be short perl or shell scripts. These would be invoked once or once per instance. One way would be to have a large script which would be edited for each release, adding or deleting code as needed. This is the way it worked in the past - the file quickly becomes "unruly". However, we would only have to touch Makefile.am once to add the upgrade script. Another way would be to have small scripts that could come and go with each release. The disadvantage is that we would be constantly adding/deleting items from Makefile.am. This is what I would prefer. Before invoking the update scripts, the code would create some sort of context, containing information about the config directory, each instance, and an identity and credentials that can be used to manage each instance. For example, when you run setup-ds-admin.pl -u, it uses the uid=admin identity and asks for the password, then uses that identity to manage each instance. However, in the case where there is just the base ds package, we would need some way to ask or specify the identity for each instance. For the UI, I don't think there's any way around just simply asking for the username and password for each instance (we can default the username to directory manager or the last value specified). For .inf file usage, I was thinking about adding a new section - [slapd-instancename] - in which you could specify the RootDN and RootDNPwd.

2 4

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

389-devel September 2009