Re: bind-chroot, runs, works, dies

Am 30.08.2017 um 15:21 schrieb Tony Finch: Petr Mensik wrote: But presence of pid files also work as notification of completed initialization (which is done BEFORE forking and finishing ExecStart command). named writes its pidfile relatively early during startup. The

Re: bind-chroot, runs, works, dies

Petr Mensik wrote: > > But presence of pid files also work as notification of completed > initialization (which is done BEFORE forking and finishing ExecStart > command). named writes its pidfile relatively early during startup. The parent doesn't exit until the child daemon

Re: bind-chroot, runs, works, dies

etr Menšík Software Engineer Red Hat, http://www.redhat.com/ email: pemen...@redhat.com PGP: 65C6C973 - Original Message - From: "Reindl Harald" <h.rei...@thelounge.net> To: bind-users@lists.isc.org Sent: Friday, August 11, 2017 4:04:12 PM Subject: Re: bind-chroot, runs, works, d

Re: bind-chroot, runs, works, dies

Am 11.08.2017 um 15:57 schrieb Petr Mensik: Hi Todd. I think much better than Ask Fedora would be filling a bug in bugzilla.redhat.com. I would see it straight away. I am Fedora bind maintainer. If there is bug preventing correct start of named-chroot, I would like to fix it. You would see

Re: bind-chroot, runs, works, dies

Hi Todd. I think much better than Ask Fedora would be filling a bug in bugzilla.redhat.com. I would see it straight away. I am Fedora bind maintainer. If there is bug preventing correct start of named-chroot, I would like to fix it. You would see SElinux errors in command "ausearch -i -ts

Re: bind-chroot, runs, works, dies

On 08/09/2017 03:28 PM, /dev/rob0 wrote: Your issue might more effectively be dealt with in a Fedora forum, or as a Fedora bug. Tried that to no avail: both Ask Fedora and Fedora Forum But Reindl knew what to do and it fix the thing. It now runs so smooth it is like poetry.

Re: bind-chroot, runs, works, dies

On 08/09/2017 03:28 PM, /dev/rob0 wrote: Your mail client has a problem with line wrapping, which made this very difficult to read. Ya, no fooling. That would be Zoho's web mail. I had to post from the field. I am back in station on Thunderbird now.

RE: bind-chroot, runs, works, dies

-users [mailto:bind-users-boun...@lists.isc.org] On Behalf Of Reindl Harald Sent: Wednesday, August 09, 2017 6:48 PM To: bind-users@lists.isc.org Subject: Re: bind-chroot, runs, works, dies Am 10.08.2017 um 00:35 schrieb Darcy Kevin (FCA): > I’m not very familiar with Fedora, but on Redhat, at le

Re: bind-chroot, runs, works, dies

that did the trick. Thank you On Wed, 09 Aug 2017 15:19:02 -0700 Reindl Haraldh.rei...@thelounge.net wrote [Service] Type=simple ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this

Re: bind-chroot, runs, works, dies

Am 10.08.2017 um 00:35 schrieb Darcy Kevin (FCA): I’m not very familiar with Fedora, but on Redhat, at least, there is no /run directory don't get me wrong but you are missing some years - /run is a important part of the system for a long time because it is a) tmpfs and b) available at

RE: bind-chroot, runs, works, dies

I’m not very familiar with Fedora, but on Redhat, at least, there is no /run directory. Which makes me think that “/var/named/chroot/run/named/named.pid” is a misconfiguration. That would be seen as “/run/named/named.pid” from *within* the chroot. Following usual conventions, I think you

Re: bind-chroot, runs, works, dies

On Wed, Aug 09, 2017 at 03:14:00PM -0700, toddandmargo wrote: > Help! > > Fedora 26 x64 > Xfce 4.12 > > # rpm -qa \bind\* > bind-libs-lite-9.11.1-2.P2.fc26.x86_64 > bind99-libs-9.9.10-1.P2.fc26.x86_64 > bind-chroot-9.11.1-2.P2.fc26.x86_64 > bind-license-9.11.1-2.P2.fc26.noarch >

Re: bind-chroot, runs, works, dies

Am 10.08.2017 um 00:14 schrieb toddandmargo: I have a weird one. I am trying to set up bind-chroot. When I run it, it works for about 30 seconds, then dies. And for the entire 30 seconds, it works beautifully. I can go anywhere with Firefox and look up anything with "host". Then it breaks