Great job, much improved!
From: 389-users-boun...@lists.fedoraproject.org
[mailto:389-users-boun...@lists.fedoraproject.org] On Behalf Of Mark Reynolds
Sent: August-25-14 2:00 PM
To: General discussion list for the 389 Directory server project.;
389-annou...@lists.fedoraproject.org
Subject:
I'm a little confused about the different versions of 389 that are available.
I followed the documentation on the Downloads page and I see the newest version
of ds-base available is 1.2.11.29-1.el6 (for RHEL6), but I also see a bunch of
1.3.x versions on the main page (including release
When I restart the dirsrv-admin process on my 389 server, any attempt to login
to the 389-console with my LDAP user ID fails with the following message:
Cannot logon because of an incorrect User ID, Incorrect Password or Directory
problem
HttpException:
Response: HTTP/1.1 401 Authorization
When adding a group from the 389-console, it creates a groupOfUniqueNames
object. I'm curious if it's possible to change it so that by default only a
posixGroup object is created and/or the group icon is displayed for posixGroup
type objects instead.
Thanks,
Ryan
--
389 users mailing list
Just upgraded my packages from:
389-ds-console-1.2.6-1.el5
389-console-1.1.7-1.el5
389-ds-console-doc-1.2.6-1.el5
389-admin-console-1.1.8-1.el5
389-admin-console-doc-1.1.8-1.el5
389-ds-base-1.2.9.9-1.el5
389-dsgw-1.1.7-2.el5
389-adminutil-1.1.14-1.el5
389-admin-1.1.23-1.el5
: [389-users] Upgraded 389-admin rpms and now I can't start
dirsrv-admin
On 01/23/2014 11:47 AM, Groten, Ryan wrote:
Just upgraded my packages from:
389-ds-console-1.2.6-1.el5
389-console-1.1.7-1.el5
389-ds-console-doc-1.2.6-1.el5
389-admin-console-1.1.8-1.el5
389-admin-console-doc-1.1.8-1.el5
389-ds
On RedHat Linux I did this by adding an entry to /etc/security/access.conf to
allow certain groups to login.
Here's what mine looks like:
# grep -v ^# /etc/security/access.conf
+ : safull sagroup2 : ALL
- : saldap : ALL
Safull is the group that is allowed access to that server, I also put
Hi all,
I'm testing out setting up 2 read-only consumers (each matches 1 of 2
multi-masters). Seems to be working fine, but I'm just trying to wrap my head
around what's happening when changes are made:
1. Have 2 multi-master Directory Servers (1.2.9.9) setup and running
2.
.
Cc: Groten, Ryan
Subject: Re: [389-users] How do read-only consumers work?
On 02/09/2012 11:24 AM, Groten, Ryan wrote:
Hi all,
I'm testing out setting up 2 read-only consumers (each matches 1 of 2
multi-masters). Seems to be working fine, but I'm just trying to wrap my head
around what's
Ok so to stop updates just don't let the clients through the firewall. To
allow updates I'd investigate the ChainOnUpdate method. Thanks Rich
From: Rich Megginson [mailto:rmegg...@redhat.com]
Sent: Thursday, February 09, 2012 11:38 AM
To: Groten, Ryan
Cc: General discussion list for the 389
From: Rich Megginson [mailto:rmegg...@redhat.com]
Sent: Tuesday, January 03, 2012 4:18 PM
To: Groten, Ryan
Cc: General discussion list for the 389 Directory server project.
Subject: Re: [389-users] bak2db restore got stuck in infinite loop
On 01/03/2012 03:50 PM, Groten, Ryan wrote:
From
From: Rich Megginson [mailto:rmegg...@redhat.com]
Sent: Tuesday, January 03, 2012 3:42 PM
To: General discussion list for the 389 Directory server project.
Cc: Groten, Ryan
Subject: Re: [389-users] bak2db restore got stuck in infinite loop
On 01/03/2012 03:14 PM, Groten, Ryan wrote:
Hi everyone
Hi everyone,
In my environment I have a total of 4 directory servers, 2 multi-masters in
production (ServerA, ServerB) and 2 multi-masters to test with (ServerC,
ServerD). Basically here's what I did:
1. Took a backup of one of the production directory servers, ServerA
2. Copied
13 matches
Mail list logo
