On Wed, 27 Jan 2016, Jon wrote:
Hi Alexander,
Huzzah!
Thanks for explaining how gethostname() works. At least armed with this
information I can make a case to the powers that be why we need to make a
change like this.
So does this mean that all servers should have a fqdn in /etc/hostname or
i
Hi Alexander,
Huzzah!
Thanks for explaining how gethostname() works. At least armed with this
information I can make a case to the powers that be why we need to make a
change like this.
So does this mean that all servers should have a fqdn in /etc/hostname or
in the case of RHEL6 setting the HO
On Wed, 27 Jan 2016, Jon wrote:
Hi Alexander,
I've changed the names to anonymize the logs, but have maintained the
structure of the names.
This is how I've got the hostname configured:
[root@freeipaserver ~]# hostname
freeipaserver
[root@freeipaserver ~]# hostname -a
freeipaserver
[root@free
Hi Alexander,
I've changed the names to anonymize the logs, but have maintained the
structure of the names.
This is how I've got the hostname configured:
>> [root@freeipaserver ~]# hostname
>> freeipaserver
>> [root@freeipaserver ~]# hostname -a
>> freeipaserver
>> [root@freeipaserver ~]# hostna
On Wed, 27 Jan 2016, Jon wrote:
Hello,
Thanks for your feedback.
So I reran `ipa-adtrust-install` and got a core dump from samba that there
was no space left on the device...?
A little digging showed that /var/log had filled up with files named
"core.X" in /var/log/samba/cores/winbindd. S
Hello,
Thanks for your feedback.
So I reran `ipa-adtrust-install` and got a core dump from samba that there
was no space left on the device...?
A little digging showed that /var/log had filled up with files named
"core.X" in /var/log/samba/cores/winbindd. So I removed all of them
and reran
On Wed, 20 Jan 2016, Anon Lister wrote:
So I had the same problem. For me it ended up being that some attribute was
not created correctly in 389 using the instructions in the guide. I don't
remember what it was off the top of my head. Something about a default user
or group SID I think. Had to tu
So I had the same problem. For me it ended up being that some attribute was
not created correctly in 389 using the instructions in the guide. I don't
remember what it was off the top of my head. Something about a default user
or group SID I think. Had to turn samba logging up. Eventually it shows t
