On (22/05/14 15:32), Daniel Jung wrote:
>(Fri May 23 00:30:33 2014) [sssd] [service_send_ping] (4): Pinging LDAP
>(Fri May 23 00:30:33 2014) [sssd] [service_send_ping] (4): Pinging nss
>(Fri May 23 00:30:33 2014) [sssd] [service_send_ping] (4): Pinging pam
>(Fri May 23 00:30:33 2014) [sssd] [ping_c
On 22/05/14 23:04, Lukas Slebodnik wrote:
On (22/05/14 22:36), steve wrote:
automount fails with both versions of the maps. Worked fine with both
openSUSE 13.1 and Ubuntu 14.04 with sssd 1.11.4
[sssd]
services = nss, pam, autofs
config_file_version = 2
domains = hh3.site
[nss]
[pam]
[domain/hh3
On 22/05/14 23:04, Lukas Slebodnik wrote:
On (22/05/14 22:36), steve wrote:
automount fails with both versions of the maps. Worked fine with both
openSUSE 13.1 and Ubuntu 14.04 with sssd 1.11.4
[sssd]
services = nss, pam, autofs
config_file_version = 2
domains = hh3.site
[nss]
[pam]
[domain/hh3
(Fri May 23 00:30:33 2014) [sssd] [service_send_ping] (4): Pinging LDAP
(Fri May 23 00:30:33 2014) [sssd] [service_send_ping] (4): Pinging nss
(Fri May 23 00:30:33 2014) [sssd] [service_send_ping] (4): Pinging pam
(Fri May 23 00:30:33 2014) [sssd] [ping_check] (4): Service LDAP replied to
ping
(Fri
On (22/05/14 22:36), steve wrote:
>automount fails with both versions of the maps. Worked fine with both
>openSUSE 13.1 and Ubuntu 14.04 with sssd 1.11.4
>
>[sssd]
>services = nss, pam, autofs
>config_file_version = 2
>domains = hh3.site
>[nss]
>[pam]
>[domain/hh3.site]
>id_provider = ad
>auth_prov
Hi Jakub,
I was curious on how the servers with same priority with weights were
implemented, the wording in RFC on this algorithm was a bit hard to
visualize for me and whether this was strictly followed. Also, at which
timeout setting is applied for cases where selected server is not reachable
an
automount fails with both versions of the maps. Worked fine with both
openSUSE 13.1 and Ubuntu 14.04 with sssd 1.11.4
[sssd]
services = nss, pam, autofs
config_file_version = 2
domains = hh3.site
[nss]
[pam]
[domain/hh3.site]
id_provider = ad
auth_provider = ad
access_provider = ad
ldap_id_mappi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/22/2014 09:28 AM, Rowland Penny wrote:
> On 22/05/14 14:06, Stephen Gallagher wrote: On 05/22/2014 08:55 AM,
> Rowland Penny wrote:
On 22/05/14 13:50, John Hodrien wrote:
> On Thu, 22 May 2014, Rowland Penny wrote:
>
>> Not on U
On 22/05/14 15:23, Rowland Penny wrote:
On 22/05/14 14:18, steve wrote:
On 22/05/14 15:10, Rowland Penny wrote:
On 22/05/14 14:05, steve wrote:
On 22/05/14 14:50, John Hodrien wrote:
On Thu, 22 May 2014, Rowland Penny wrote:
Not on Ubuntu it isn't ;-)
I'd argue that Ubuntu just has incorr
On 22/05/14 14:28, steve wrote:
On 22/05/14 14:43, Rowland Penny wrote:
@Rowland
Sorry to trouble.
We've messed up nsswitch
Can you send your working version of:
hosts: files mdns_minimal [NOTFOUND=return] dns
or whatever is the right answer?
Our line is working but several of us have l
On 22/05/14 14:06, Stephen Gallagher wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/22/2014 08:55 AM, Rowland Penny wrote:
On 22/05/14 13:50, John Hodrien wrote:
On Thu, 22 May 2014, Rowland Penny wrote:
Not on Ubuntu it isn't ;-)
I'd argue that Ubuntu just has incorrect behavio
On 22/05/14 14:43, Rowland Penny wrote:
@Rowland
Sorry to trouble.
We've messed up nsswitch
Can you send your working version of:
hosts: files mdns_minimal [NOTFOUND=return] dns
or whatever is the right answer?
Our line is working but several of us have left commented rubbish there.
Chee
On 22/05/14 14:18, steve wrote:
On 22/05/14 15:10, Rowland Penny wrote:
On 22/05/14 14:05, steve wrote:
On 22/05/14 14:50, John Hodrien wrote:
On Thu, 22 May 2014, Rowland Penny wrote:
Not on Ubuntu it isn't ;-)
I'd argue that Ubuntu just has incorrect behaviour then.
If you look at man h
On 22/05/14 15:10, Rowland Penny wrote:
On 22/05/14 14:05, steve wrote:
On 22/05/14 14:50, John Hodrien wrote:
On Thu, 22 May 2014, Rowland Penny wrote:
Not on Ubuntu it isn't ;-)
I'd argue that Ubuntu just has incorrect behaviour then.
If you look at man hosts on an ubuntu machine (13.10)
On 22/05/14 14:05, steve wrote:
On 22/05/14 14:50, John Hodrien wrote:
On Thu, 22 May 2014, Rowland Penny wrote:
Not on Ubuntu it isn't ;-)
I'd argue that Ubuntu just has incorrect behaviour then.
If you look at man hosts on an ubuntu machine (13.10), you'll see how
they
describe it, and
On Thu, 2014-05-22 at 15:05 +0200, steve wrote:
> On 22/05/14 14:50, John Hodrien wrote:
> > On Thu, 22 May 2014, Rowland Penny wrote:
> >
> >> Not on Ubuntu it isn't ;-)
> >
> > I'd argue that Ubuntu just has incorrect behaviour then.
> >
> > If you look at man hosts on an ubuntu machine (13.10),
On 22/05/14 14:50, John Hodrien wrote:
On Thu, 22 May 2014, Rowland Penny wrote:
Not on Ubuntu it isn't ;-)
I'd argue that Ubuntu just has incorrect behaviour then.
If you look at man hosts on an ubuntu machine (13.10), you'll see how they
describe it, and the example they provide. The form
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/22/2014 08:55 AM, Rowland Penny wrote:
> On 22/05/14 13:50, John Hodrien wrote:
>> On Thu, 22 May 2014, Rowland Penny wrote:
>>
>>> Not on Ubuntu it isn't ;-)
>>
>> I'd argue that Ubuntu just has incorrect behaviour then.
>>
>> If you look at
On 22/05/14 13:50, John Hodrien wrote:
On Thu, 22 May 2014, Rowland Penny wrote:
Not on Ubuntu it isn't ;-)
I'd argue that Ubuntu just has incorrect behaviour then.
If you look at man hosts on an ubuntu machine (13.10), you'll see how
they
describe it, and the example they provide. The fo
On Thu, 22 May 2014, Rowland Penny wrote:
Not on Ubuntu it isn't ;-)
I'd argue that Ubuntu just has incorrect behaviour then.
If you look at man hosts on an ubuntu machine (13.10), you'll see how they
describe it, and the example they provide. The format described is:
IP_address canonical_h
On 22/05/14 13:38, John Hodrien wrote:
On Thu, 22 May 2014, steve wrote:
/etc/hostname has to contain the fqdn, not the hostname. So now,
hostname
is wrong
but
hostname -s
and
hostname -f
return correctly.
More importantly, the ddns updates go fine.
However, I'm sure that'll break something el
On Thu, 22 May 2014, steve wrote:
/etc/hostname has to contain the fqdn, not the hostname. So now,
hostname
is wrong
but
hostname -s
and
hostname -f
return correctly.
More importantly, the ddns updates go fine.
However, I'm sure that'll break something else somewhere else down the line.
What i
On 22/05/14 12:41, steve wrote:
On 22/05/14 12:37, steve wrote:
On 21/05/14 22:14, Jakub Hrozek wrote:
On Wed, May 21, 2014 at 09:07:23PM +0200, steve wrote:
So why does nsupdate work but sssd doesn't?
OK,
Fixed it, but we don't like it:
/etc/hostname has to contain the fqdn, not the hostnam
On 22/05/14 12:37, steve wrote:
On 21/05/14 22:14, Jakub Hrozek wrote:
On Wed, May 21, 2014 at 09:07:23PM +0200, steve wrote:
So why does nsupdate work but sssd doesn't?
Can you show me how do you invoke nsupdate manually ?
(sssd just invokes nsupate itself, so it must be some difference in
t
On 21/05/14 22:14, Jakub Hrozek wrote:
On Wed, May 21, 2014 at 09:07:23PM +0200, steve wrote:
So why does nsupdate work but sssd doesn't?
Can you show me how do you invoke nsupdate manually ?
(sssd just invokes nsupate itself, so it must be some difference in the
command file I guess).
Simo.
25 matches
Mail list logo
