On 04/06/2016 07:03 PM, Chris Murphy wrote:
On Wed, Apr 6, 2016, 2:07 AM Samuel Sieb > wrote:
On 04/06/2016 12:58 AM, Tim wrote:
> On Tue, 2016-04-05 at 16:32 -0700, Samuel Sieb wrote:
>> One important issue is that you can't install to the
On Wed, Apr 6, 2016, 2:07 AM Samuel Sieb wrote:
> On 04/06/2016 12:58 AM, Tim wrote:
> > On Tue, 2016-04-05 at 16:32 -0700, Samuel Sieb wrote:
> >> One important issue is that you can't install to the drive
> >> that you read the iso from
> >
> > "Partition" not "drive".
> >
>
On Sun, 2016-04-03 at 18:09 +0200, Graham Leggett wrote:
> Hi all,
>
> I have a 389ds v1.3.4 server as deployed by CentOS7 configured with SSL/TLS to
> require client certificates.
>
> Attempts to connect to this server using “openssl s_client” fail, and the
> failure is triggered by the 389ds
On Wed, 2016-04-06 at 12:03 +, warron.fre...@gmail.com wrote:
> Good morning Mr. Brown,
>
> Here is the results of your first query; executing the certutil command as you
> presented it (with adding my instance):
> certutil -L -d /etc/dirsrv/slapd-E2WAN/
>
> Certificate Nickname
On Wed, 2016-04-06 at 21:12 +, anteneh assen wrote:
> 389 DS documentation link refers to the commercial Redhat DS, does all the
> features mentioned in the Redhat DS available in 389 DS?
Yes.
--
Sincerely,
William Brown
Software Engineer
Red Hat, Brisbane
signature.asc
Description:
On 04/06/2016 03:28 PM, Tom Horsley wrote:
On Wed, 6 Apr 2016 15:15:07 -0700
Rick Stevens wrote:
Any info buried in the journals? Perhaps there's a more complete error
in there somewhere.
Not that I noticed anywhere. I did trace dnf doing this, and found
that despite the error message
On Wed, 6 Apr 2016 15:15:07 -0700
Rick Stevens wrote:
> Any info buried in the journals? Perhaps there's a more complete error
> in there somewhere.
Not that I noticed anywhere. I did trace dnf doing this, and found
that despite the error message starting with the string "cpio:" that
no cpio is
On 04/06/2016 02:11 PM, Tom Horsley wrote:
On Wed, 06 Apr 2016 12:55:04 -0700
Doug H. wrote:
So my guess is that there is a digest file that is being checked by
default in fedora but not checked on centos.
But I'd really like to know why it says it has a problem.
We use rpmbuild on a fairly
389 DS documentation link refers to the commercial Redhat DS, does all the
features mentioned in the Redhat DS available in 389 DS?
--
389 users mailing list
389-users@%(host_name)s
http://lists.fedoraproject.org/admin/lists/389-users@lists.fedoraproject.org
On Wed, 06 Apr 2016 12:55:04 -0700
Doug H. wrote:
> So my guess is that there is a digest file that is being checked by
> default in fedora but not checked on centos.
But I'd really like to know why it says it has a problem.
We use rpmbuild on a fairly old RHEL build system to create
the
Graham, you are probably a great deal more seasoned at this software than I am,
but have you tried running the ldapsearch command in debug mode?
Maybe you will find that your certs are expired, or in a weird place (which I
am trying to learn how to adjust).
Just a thought from someone who
On Mon, 2016-04-04 at 08:38 -0400, Tom Horsley wrote:
> Anyone have any idea why only fedora systems would give this
> error installing an rpm?
>
> Installing : ccur-ntrace-ai-7.5-
> 0.beta.75.x86_6419/32
> Error unpacking rpm package ccur-ntrace-ai-7.5-0.beta.75.x86_64
Good morning Mr. Brown,
Here is the results of your first query; executing the certutil command as you
presented it (with adding my instance):
certutil -L -d /etc/dirsrv/slapd-E2WAN/
Certificate Nickname Trust Attributes
On Wed, 06 Apr 2016 00:04:28 +1000
"Michael D. Setzer II" wrote:
> I just got 4 usb 802.11n nics, and they were not recognized by fedora 23??
> Windows 10 did seem to have no problems, and they are rtl8192eu.
>
> Did find a page that talked about getting them to work,
On 04/06/2016 12:58 AM, Tim wrote:
On Tue, 2016-04-05 at 16:32 -0700, Samuel Sieb wrote:
One important issue is that you can't install to the drive
that you read the iso from
"Partition" not "drive".
No, I definitely mean drive. If you put the iso file in /home and try
to use it as the
On 04/06/2016 08:30 AM, wodel youchi wrote:
Hi,
is it possible to configure 389DS to give some attributes default values?
We're migrating from openLDAP to 389DS, which will be used to
authenticate mail users, we want to give for example *mailQuota* a
default value for new accounts.
in 389ds
On Tue, 2016-04-05 at 16:32 -0700, Samuel Sieb wrote:
> One important issue is that you can't install to the drive
> that you read the iso from
"Partition" not "drive".
--
tim@localhost ~]$ uname -rsvp
Linux 3.19.8-100.fc20.i686 #1 SMP Tue May 12 17:42:35 UTC 2015 i686
All mail to my
Hi,
is it possible to configure 389DS to give some attributes default values?
We're migrating from openLDAP to 389DS, which will be used to authenticate
mail users, we want to give for example *mailQuota* a default value for new
accounts.
is this possible?
Regards.
--
389 users mailing list
18 matches
Mail list logo