One some of my nodes, attempting to sudo yields this:
$ sudo su -
sudo: ldap_start_tls_s(): Connect error
[sudo] password for bretw:
When the policy for my account is set up for !authenticate on all systems.
On my own workstation, and most of our systems, it works just fine. But on
a few, this
Bret Wortman wrote:
One some of my nodes, attempting to sudo yields this:
$ sudo su -
sudo: ldap_start_tls_s(): Connect error
[sudo] password for bretw:
When the policy for my account is set up for !authenticate on all systems.
On my own workstation, and most of our systems, it works just
Thanks. In this case, on a lark, I compared the sizes of the ca.crt file
between the working and nonworking nodes and there was a 4 byte difference.
Copying over the working copy to the nonworking node got things flowing
again. I'm filing these notes in my nv stack for later reference, though.
Hello list,
we would like to get more details about DNS views and how you use them in real
life. Also, any idea how user a interface should work is more than welcome!
(If you don't know views, read it as differentiate answer to a DNS query on
client's IP address basics.)
Questions are:
-
On 10/01/2013 09:11 AM, Petr Spacek wrote:
Hello list,
we would like to get more details about DNS views and how you use them
in real life. Also, any idea how user a interface should work is more
than welcome!
(If you don't know views, read it as differentiate answer to a DNS
query on client's
Hi,
On Tue, Oct 01, 2013 at 05:11:16PM +0200, Petr Spacek wrote:
Questions are:
- For what purpose do you use views?
I see only use for 2 views:
a) Internal clients, domain members. They
- see everything (internet DNS records plus IPA domain
data)
- can request
