On 07/12/18 09:45, Ed Greshko wrote:
> On 07/12/18 08:27, Tom Horsley wrote:
>> I ssh into my fedora 28 system at work, I get this printed
>> when I login:
>>
>> zooty> ssh -l tweety tomh8022
>> --
>> /etc/motd printed here
>>
On 07/12/18 08:27, Tom Horsley wrote:
> I ssh into my fedora 28 system at work, I get this printed
> when I login:
>
> zooty> ssh -l tweety tomh8022
> --
> /etc/motd printed here
>
On 07/11/2018 03:16 PM, Stephen Morris wrote:
> On 11/7/18 8:47 am, Samuel Sieb wrote:
>> On 07/10/2018 03:17 PM, Stephen Morris wrote:
>>> 1). Can anyone shed any light on why the install may have failed and
>>> what I need to do to work around it? I'm hoping I don't have to run a
>>> 'sudo dnf
On Thu, 12 Jul 2018 08:16:06 +1000
Stephen Morris wrote:
> Both with the F28 kernel, being 4.17.3-200, and the F27 kernel I
> mentioned, the compile fails with stdarg.h not found, so I'm now
> confused about what the F28 upgrade has done. The F28 upgrade should
> not have updated the F27 kernel
On 12/7/18 8:38 am, Rick Stevens wrote:
On 07/11/2018 03:16 PM, Stephen Morris wrote:
On 11/7/18 8:47 am, Samuel Sieb wrote:
On 07/10/2018 03:17 PM, Stephen Morris wrote:
1). Can anyone shed any light on why the install may have failed and
what I need to do to work around it? I'm hoping I
On Wed, Jul 11, 2018 at 8:37 PM Tom Horsley wrote:
> I ssh into my fedora 28 system at work, I get this printed
> when I login:
>
> zooty> ssh -l tweety tomh8022
> --
> /etc/motd printed here
>
Stephen Morris writes:
and that installed all the package updates that caused the conflicts. Having
done this I was able to complete the upgrade to F28, but now I have big
problems.
Under F28 my USB network device doesn't work because dkms can't compile the
driver for it, and, either
I ssh into my fedora 28 system at work, I get this printed
when I login:
zooty> ssh -l tweety tomh8022
--
/etc/motd printed here
--
Last login: Wed Jul 11 20:21:39 2018 from
On 11/7/18 8:47 am, Samuel Sieb wrote:
On 07/10/2018 03:17 PM, Stephen Morris wrote:
1). Can anyone shed any light on why the install may have failed and
what I need to do to work around it? I'm hoping I don't have to run a
'sudo dnf clean all' and then a 'sudo dnf system-upgrade --refresh
On 07/11/2018 03:16 PM, Stephen Morris wrote:
On 11/7/18 8:47 am, Samuel Sieb wrote:
On 07/10/2018 03:17 PM, Stephen Morris wrote:
2). Where can I find the logs that would contain the error message so
I can read what it said, given that /var/log/boot.log and
/var/log/dnf.log both don't
Yeah, my plan is to setup a replication agreement. That way I don't have to do
multiple imports. I need the old and new servers to stay in sync until the
cutover.
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an
I have a current 389 deployment that I need to duplicate to a new set of
servers to be used at a different facility on a different network. I'm
thinking that I could either do an import or use replication. My plan is to
use replication to replicate the data to the new set of servers. That
Does anyone use keepalived with a mult-master setup? I'm currently using an
haproxy, but I think just using a vip between the two masters should be
sufficient for my use case. I'm curious how keepalived would work with a 389
server.
___
389-users
Hi List
I am looking to cfg nsIdleTimeout attribute for a specific DS user, I tryed
using 389-console and ldapmodify but I not successful, in 389-console this
attribute is in grey when trying to add a value will not allowed , with
ldapmodify nothing happened no prompt or error given back but
On 07/11/2018 03:20 PM, Ghiurea, Isabella wrote:
Hi List
I am looking to cfg nsIdleTimeout attribute for a specific DS user, I
tryed using 389-console and ldapmodify but I not successful, in
389-console this attribute is in grey when trying to add a value will
not allowed , with
On Wed, 2018-07-11 at 19:03 +, Brian Lehnhardt wrote:
> Does anyone use keepalived with a mult-master setup? I'm currently
> using an haproxy, but I think just using a vip between the two
> masters should be sufficient for my use case. I'm curious how
> keepalived would work with a 389
On Tue, 2018-06-26 at 22:39 +, Mitch Patenaude wrote:
> Our organization’s security policies impose several constraints on
> password changes. There is a complexity requirement, and a ban on
> reuse of old passwords. I’ve gotten all of these requirements worked
> into the 389 server, but
On Wed, 2018-07-11 at 16:05 -0400, Mark Reynolds wrote:
>
>
> On 07/11/2018 03:20 PM, Ghiurea, Isabella wrote:
> > Hi List
> > I am looking to cfg nsIdleTimeout attribute for a specific DS
> > user, I tryed using 389-console and ldapmodify but I not
> > successful, in 389-console this attribute
18 matches
Mail list logo
