FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Directory

 
 
LinkBack Thread Tools
 
Old 03-26-2011, 02:44 AM
彭胜文
 
Default Announcing 389 Directory Server version 1.2.8 Release Candidate 2

hi,
*support centos 5.x or redhat 6.0* ?
***
--
BR,
Thanks!

> -----原始邮件-----
> 发件人: "Rich Megginson" <rmeggins@redhat.com>
> 发送时间: 2011年3月26日 星期*
> 收件人: 389-announce@lists.fedoraproject.org, 389-users@lists.fedoraproject.org
> 抄送:
> 主题: [389-users] Announcing 389 Directory Server version 1.2.8 Release Candidate 2
>
> The 389 Project team is pleased to announce the release of
> 389-ds-base-1.2.8 Release Candidate 2. This release has fixes for bugs
> found in 1.2.8 testing and bugs from earlier releases.
>
> Installation
>
> yum install --enablerepo=updates-testing 389-ds
> # or for EPEL
> yum install --enablerepo=epel-testing 389-ds
> setup-ds-admin.pl
>
> Upgrade
>
> yum upgrade --enablerepo=updates-testing 389-ds-base
> idm-console-framework 389-admin 389-ds-console 389-admin-console
> # or for EPEL
> yum upgrade --enablerepo=epel-testing 389-ds-base
> idm-console-framework 389-admin 389-ds-console 389-admin-console
> setup-ds-admin.pl -u
>
> How to Give Feedback
>
> The best way to provide feedback is via the Fedora Update system. Each
> update is broken down by package and platform. For example, if you are
> using Fedora 13, and you have successfully installed or upgraded all of
> the packages, and the console and etc. works, then go to the links below
> for Fedora 13 and provide feedback.
>
> * EL-5 -
> https://admin.fedoraproject.org/updates/389-ds-base-1.2.8-0.7.rc2.el5
> * Fedora 13 -
> https://admin.fedoraproject.org/updates/389-ds-base-1.2.8-0.7.rc2.fc13
> * Fedora 14 -
> https://admin.fedoraproject.org/updates/389-ds-base-1.2.8-0.7.rc2.fc14
> * Fedora 15 -
> https://admin.fedoraproject.org/updates/389-ds-base-1.2.8-0.8.rc2.fc15
>
> scroll down to the bottom of the page, and click on the Add a comment >>
> link
>
> * select one of the Works for me or Does not work radio buttons, add
> text, and click on the Add Comment button
>
> If you are using a build on another platform, just send us an email to
> 389-users@lists.fedoraproject.org
>
> Reporting Bugs
>
> If you find a bug, or would like to see a new feature, you can enter it
> here - https://bugzilla.redhat.com/enter_bug.cgi?product=389
>
> More Information
> * Release Notes - http://port389.org/wiki/Release_Notes
> * Install_Guide - http://port389.org/wiki/Install_Guide
> * Download - http://port389.org/wiki/Download
>
>
> --
> 389 users mailing list
> 389-users@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/389-users


--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
 
Old 03-28-2011, 01:23 PM
Rich Megginson
 
Default Announcing 389 Directory Server version 1.2.8 Release Candidate 2

On 03/25/2011 09:44 PM, *胜文 wrote:
hi,

*support centos 5.x or redhat 6.0* ?



Any EL5 - rhel, centos, scientific, etc. should work



There is no support for EL6


*
*
*
--
BR,
Thanks!

> -----原始邮件-----
> 发件人: "Rich Megginson" <rmeggins@redhat.com>
> 发送时间: 2011年3月26日 星期*
> 收件人: 389-announce@lists.fedoraproject.org, 389-users@lists.fedoraproject.org
> 抄送:
> 主题: [389-users] Announcing 389 Directory Server version 1.2.8 Release Candidate 2
>
> The 389 Project team is pleased to announce the release of
> 389-ds-base-1.2.8 Release Candidate 2. This release has fixes for bugs
> found in 1.2.8 testing and bugs from earlier releases.
>
> Installation
>
> yum install --enablerepo=updates-testing 389-ds
> # or for EPEL
> yum install --enablerepo=epel-testing 389-ds
> setup-ds-admin.pl
>
> Upgrade
>
> yum upgrade --enablerepo=updates-testing 389-ds-base
> idm-console-framework 389-admin 389-ds-console 389-admin-console
> # or for EPEL
> yum upgrade --enablerepo=epel-testing 389-ds-base
> idm-console-framework 389-admin 389-ds-console 389-admin-console
> setup-ds-admin.pl -u
>
> How to Give Feedback
>
> The best way to provide feedback is via the Fedora Update system. Each
> update is broken down by package and platform. For example, if you are
> using Fedora 13, and you have successfully installed or upgraded all of
> the packages, and the console and etc. works, then go to the links below
> for Fedora 13 and provide feedback.
>
> * EL-5 -
> https://admin.fedoraproject.org/updates/389-ds-base-1.2.8-0.7.rc2.el5
> * Fedora 13 -
> https://admin.fedoraproject.org/updates/389-ds-base-1.2.8-0.7.rc2.fc13
> * Fedora 14 -
> https://admin.fedoraproject.org/updates/389-ds-base-1.2.8-0.7.rc2.fc14
> * Fedora 15 -
> https://admin.fedoraproject.org/updates/389-ds-base-1.2.8-0.8.rc2.fc15
>
> scroll down to the bottom of the page, and click on the Add a comment >>
> link
>
> * select one of the Works for me or Does not work radio buttons, add
> text, and click on the Add Comment button
>
> If you are using a build on another platform, just send us an email to
> 389-users@lists.fedoraproject.org
>
> Reporting Bugs
>
> If you find a bug, or would like to see a new feature, you can enter it
> here - https://bugzilla.redhat.com/enter_bug.cgi?product=389
>
> More Information
> * Release Notes - http://port389.org/wiki/Release_Notes
> * Install_Guide - http://port389.org/wiki/Install_Guide
> * Download - http://port389.org/wiki/Download
>
>
> --
> 389 users mailing list
> 389-users@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/389-users








--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users





--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
 
Old 03-30-2011, 12:30 PM
Andrey Ivanov
 
Default Announcing 389 Directory Server version 1.2.8 Release Candidate 2

Hi Rich,

2011/3/25 Rich Megginson <rmeggins@redhat.com>:
> The 389 Project team is pleased to announce the release of
> 389-ds-base-1.2.8 Release Candidate 2. *This release has fixes for bugs
> found in 1.2.8 testing and bugs from earlier releases.

i've made a rapid test compiling from today's sources (1.2.8.rc3 or
rc4 i think). I haven't seen any immediately obvious bugs. It is also
much more stable than 1.2.7.5.


However i've noticed that the order of operations in logs is not
always correct :

[30/Mar/2011:14:17:03 +0200] conn=13 fd=128 slot=128 connection from
127.0.0.1 to 127.0.0.1
[30/Mar/2011:14:17:03 +0200] conn=13 op=0 BIND dn="" method=128 version=3
[30/Mar/2011:14:17:03 +0200] conn=13 op=1 SRCH
base="dc=id,dc=polytechnique,dc=edu" scope=2
filter="(&(|(objectClass=X-Misc)(objectClass=X-Object))(!(X-UniqueId=*)))"
attrs="nsUniqueId"
[30/Mar/2011:14:17:03 +0200] conn=13 op=1 RESULT err=0 tag=101
nentries=0 etime=0.117000 notes=U
[30/Mar/2011:14:17:03 +0200] conn=13 op=2 UNBIND
[30/Mar/2011:14:17:03 +0200] conn=13 op=2 fd=128 closed - U1
[30/Mar/2011:14:17:03 +0200] conn=13 op=0 RESULT err=0 tag=97
nentries=0 etime=0.021000 dn=""
(the result of op=0 is after op=2)

or
[30/Mar/2011:14:20:19 +0200] conn=19 fd=128 slot=128 connection from
local to /Local/dirsrv/var/run/slapd-dmz.socket
[30/Mar/2011:14:20:19 +0200] conn=19 AUTOBIND dn="cn=X LDAP Root"
[30/Mar/2011:14:20:19 +0200] conn=19 op=0 BIND dn="cn=X LDAP Root"
method=sasl version=3 mech=EXTERNAL
[30/Mar/2011:14:20:19 +0200] conn=19 op=1 SRCH
base="dc=id,dc=polytechnique,dc=edu" scope=2
filter="(&(|(objectClass=X-Misc)(objectClass=X-Object))(!(X-UniqueId=*)))"
attrs="nsUniqueId"
[30/Mar/2011:14:20:19 +0200] conn=19 op=2 UNBIND
[30/Mar/2011:14:20:19 +0200] conn=19 op=2 fd=128 closed - U1
[30/Mar/2011:14:20:19 +0200] conn=19 op=0 RESULT err=0 tag=97
nentries=0 etime=0.012000 dn="cn=X LDAP Root"
[30/Mar/2011:14:20:19 +0200] conn=19 op=1 RESULT err=0 tag=101
nentries=0 etime=0.108000 notes=U
(the result of op=0 and op=1 is after op=2)


It is not something new, i've tested on 1.2.6.1 (our production
environment) and this behavior it is also present. I observe it much
more often when the log buffering is off. Don't know if it's a bug or
it's because of several threads writing in parallel and it's an
expected phenomenon...


@+
--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
 
Old 03-30-2011, 02:28 PM
Rich Megginson
 
Default Announcing 389 Directory Server version 1.2.8 Release Candidate 2

On 03/30/2011 06:30 AM, Andrey Ivanov wrote:
> Hi Rich,
>
> 2011/3/25 Rich Megginson<rmeggins@redhat.com>:
>> The 389 Project team is pleased to announce the release of
>> 389-ds-base-1.2.8 Release Candidate 2. This release has fixes for bugs
>> found in 1.2.8 testing and bugs from earlier releases.
> i've made a rapid test compiling from today's sources (1.2.8.rc3 or
> rc4 i think). I haven't seen any immediately obvious bugs. It is also
> much more stable than 1.2.7.5.
>
>
> However i've noticed that the order of operations in logs is not
> always correct :
>
> [30/Mar/2011:14:17:03 +0200] conn=13 fd=128 slot=128 connection from
> 127.0.0.1 to 127.0.0.1
> [30/Mar/2011:14:17:03 +0200] conn=13 op=0 BIND dn="" method=128 version=3
> [30/Mar/2011:14:17:03 +0200] conn=13 op=1 SRCH
> base="dc=id,dc=polytechnique,dc=edu" scope=2
> filter="(&(|(objectClass=X-Misc)(objectClass=X-Object))(!(X-UniqueId=*)))"
> attrs="nsUniqueId"
> [30/Mar/2011:14:17:03 +0200] conn=13 op=1 RESULT err=0 tag=101
> nentries=0 etime=0.117000 notes=U
> [30/Mar/2011:14:17:03 +0200] conn=13 op=2 UNBIND
> [30/Mar/2011:14:17:03 +0200] conn=13 op=2 fd=128 closed - U1
> [30/Mar/2011:14:17:03 +0200] conn=13 op=0 RESULT err=0 tag=97
> nentries=0 etime=0.021000 dn=""
> (the result of op=0 is after op=2)
>
> or
> [30/Mar/2011:14:20:19 +0200] conn=19 fd=128 slot=128 connection from
> local to /Local/dirsrv/var/run/slapd-dmz.socket
> [30/Mar/2011:14:20:19 +0200] conn=19 AUTOBIND dn="cn=X LDAP Root"
> [30/Mar/2011:14:20:19 +0200] conn=19 op=0 BIND dn="cn=X LDAP Root"
> method=sasl version=3 mech=EXTERNAL
> [30/Mar/2011:14:20:19 +0200] conn=19 op=1 SRCH
> base="dc=id,dc=polytechnique,dc=edu" scope=2
> filter="(&(|(objectClass=X-Misc)(objectClass=X-Object))(!(X-UniqueId=*)))"
> attrs="nsUniqueId"
> [30/Mar/2011:14:20:19 +0200] conn=19 op=2 UNBIND
> [30/Mar/2011:14:20:19 +0200] conn=19 op=2 fd=128 closed - U1
> [30/Mar/2011:14:20:19 +0200] conn=19 op=0 RESULT err=0 tag=97
> nentries=0 etime=0.012000 dn="cn=X LDAP Root"
> [30/Mar/2011:14:20:19 +0200] conn=19 op=1 RESULT err=0 tag=101
> nentries=0 etime=0.108000 notes=U
> (the result of op=0 and op=1 is after op=2)
>
>
> It is not something new, i've tested on 1.2.6.1 (our production
> environment) and this behavior it is also present. I observe it much
> more often when the log buffering is off. Don't know if it's a bug or
> it's because of several threads writing in parallel and it's an
> expected phenomenon...
It might be a bug in that it would be nice if they were always in
order. It is just the logging that is out of order - the operations do
go through in the correct order.
>
> @+

--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
 

Thread Tools




All times are GMT. The time now is 06:42 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org