Re: named-chroot issue - AGAIN

On Thu, Mar 17, 2016 at 11:44 AM, Steven Haigh wrote: > On 17/03/2016 9:39 PM, Tom H wrote: >> >> You just have to override it in "/etc/systemd/system/". > > Which (as I pointed out on the bug report associated with this issue) is > a completely retarded and broken concept to

named-chroot issue - AGAIN

Hi guys Another named update and still the named-chroot.service file has not been fixed. It is really annoying to have to manually fix it every time, just to get DNS working after an update. Why is the -t /var/named/chroot option included in the ExecStart but not in the ExecStartPre

Re: named-chroot issue - AGAIN

On 17/03/16 12:40, Steven Haigh wrote: > On 17/03/2016 10:25 PM, David Sommerseth wrote: >> On 17/03/16 06:36, Bill Maidment wrote: >>> Hi guys >>> Another named update and still the named-chroot.service file has not been >>> fixed. It is really annoying to have to manually fix it every time,

Re: Setting hostname

Brandon Vincent writes: > On Mar 16, 2016 7:56 AM, "Loris Bennett" > wrote: >> >> Brandon Vincent writes: >> >> > On Mar 15, 2016 3:44 AM, "Loris Bennett" >> > wrote: >> >> What other

Re: Setting hostname

I haven't been following this email chain, but I see that you asked: Is there any way to tell that the hostname has been set via hostname some.random.address rather via some init script reading /etc/sysconfig/network? To satisfy my own curiosity I looked on an SL6.7 computer for how

Re: Setting hostname

On Mar 15, 2016 3:44 AM, "Loris Bennett" wrote: > What other files could have an influence on what 'hostname' returns? Could you post the output of getent hosts [hostname] and getent hosts [ip] for both systems? Also please post the hosts line from nsswitch.conf

Re: named-chroot issue - AGAIN

On 19/03/2016 1:31 AM, Tom H wrote: > On Thu, Mar 17, 2016 at 11:17 PM, David Sommerseth > wrote: >> On 17/03/16 13:23, Tom H wrote: >>> On Thu, Mar 17, 2016 at 12:53 PM, David Sommerseth >>> wrote: Not going to argue

Re: Setting hostname

On Wed, Mar 16, 2016 at 1:53 PM, Loris Bennett wrote: > Tom H writes: >> On Tue, Mar 15, 2016 at 1:42 PM, Nico Kadel-Garcia wrote: >>> On Tue, Mar 15, 2016 at 8:32 AM, Nico Kadel-Garcia wrote: >>> The

Re: named-chroot issue - AGAIN

On 18/03/2016 1:24 PM, Nico Kadel-Garcia wrote: > On Thu, Mar 17, 2016 at 8:23 AM, Tom H wrote: >> On Thu, Mar 17, 2016 at 12:53 PM, David Sommerseth >> wrote: >>> >>> Not going to argue that this could have been done better, I agree with you

Re: Setting hostname

On Tue, Mar 15, 2016 at 1:42 PM, Nico Kadel-Garcia wrote: > On Tue, Mar 15, 2016 at 8:32 AM, Nico Kadel-Garcia wrote: > >> The problem is that the $HOSTNAME for the system isn't published in >> DNS, nor is it the first hostname for a line in /etc/hosts, so the

Need NAS recommendations

Hi All, Anyone have a favorite small (2 to 4 TB) Network Attached Storage (NAS) that is Linux friendly. No weird drivers, etc.. Many thanks, -T -- ~~ Computers are like air conditioners. They malfunction when you open windows

Re: named-chroot issue - AGAIN

On Thu, Mar 17, 2016 at 8:23 AM, Tom H wrote: > On Thu, Mar 17, 2016 at 12:53 PM, David Sommerseth > wrote: >> >> Not going to argue that this could have been done better, I agree with you >> here. On the other hand, maybe *that* is one reason

Re: named-chroot issue - AGAIN

On 17/03/16 13:23, Tom H wrote: > On Thu, Mar 17, 2016 at 12:53 PM, David Sommerseth > wrote: >> >> Not going to argue that this could have been done better, I agree with you >> here. On the other hand, maybe *that* is one reason it takes time to get this >> issue

Re: named-chroot issue - AGAIN

On 17/03/2016 10:25 PM, David Sommerseth wrote: > On 17/03/16 06:36, Bill Maidment wrote: >> Hi guys >> Another named update and still the named-chroot.service file has not been >> fixed. It is really annoying to have to manually fix it every time, just to >> get DNS working after an update. >>

Re: named-chroot issue - AGAIN

On Thu, Mar 17, 2016 at 11:17 PM, David Sommerseth wrote: > On 17/03/16 13:23, Tom H wrote: >> On Thu, Mar 17, 2016 at 12:53 PM, David Sommerseth >> wrote: >>> >>> Not going to argue that this could have been done better, I agree

Re: livecd-tools

On 03/18/2016 04:37 PM, ToddAndMargo wrote: Hi Nux, Any change you can upgrade livecd-tools-20.1-3.el7.nux.x86_64 so I can please this guy? https://bugzilla.redhat.com/show_bug.cgi?id=1317241 FC23 is on this one: livecd-tools-23.2-3.fc23.x86_64.rpm Many thanks, -T Ooops, wrong address.

Re: named-chroot issue - AGAIN

On Thu, Mar 17, 2016 at 6:36 AM, Bill Maidment wrote: > > Another named update and still the named-chroot.service file has not > been fixed. It is really annoying to have to manually fix it every > time, just to get DNS working after an update. Why is the -t > /var/named/chroot

Re: named-chroot issue - AGAIN

On Thu, Mar 17, 2016 at 12:53 PM, David Sommerseth wrote: > > Not going to argue that this could have been done better, I agree with you > here. On the other hand, maybe *that* is one reason it takes time to get this > issue resolved too? That Red Hat QE is

Re: named-chroot issue - AGAIN

On 17/03/16 06:36, Bill Maidment wrote: > Hi guys > Another named update and still the named-chroot.service file has not been > fixed. It is really annoying to have to manually fix it every time, just to > get DNS working after an update. > Why is the -t /var/named/chroot option included in the

Re: named-chroot issue - AGAIN

On 17/03/2016 10:53 PM, David Sommerseth wrote: > On 17/03/16 12:40, Steven Haigh wrote: >> On 17/03/2016 10:25 PM, David Sommerseth wrote: >>> On 17/03/16 06:36, Bill Maidment wrote: Hi guys Another named update and still the named-chroot.service file has not been fixed. It is

Re: Setting hostname

On Mar 16, 2016 7:56 AM, "Loris Bennett" wrote: > > Brandon Vincent writes: > > > On Mar 15, 2016 3:44 AM, "Loris Bennett" > > wrote: > >> What other files could have an influence on what 'hostname' returns? > > >