Re: [Dnssec-trigger] current status?

2015-03-12 Thread Paul Wouters
On Thu, 12 Mar 2015, Chuck Anderson wrote: There is a long standing bug that triggers in certain situations with hotspots where somehow dnssec-triggerd rewrites resolv.conf but actually has no (DHCP obtained) DNS server to put in, it then writes a file without any nameserver entry and expects

Re: [Dnssec-trigger] current status?

2015-03-12 Thread Tomas Hozza
On 03/12/2015 02:31 PM, Chuck Anderson wrote: On Thu, Mar 12, 2015 at 09:20:28AM +0100, Tomas Hozza wrote: On 03/11/2015 08:21 PM, Chuck Anderson wrote: Every day after resuming from suspend, I have crash messages pop up on Fedora 21 from dnssec-trigger (even after I fixed rhbz#1187371 myself

Re: [Dnssec-trigger] current status?

2015-03-12 Thread Carsten Strotmann
Hello Chuck, Chuck Anderson writes: What is the current status of dnssec-trigger? Does anyone here run this daily on Fedora 21? I'm running dnssec-trigger (0.12) on my Thinkpad with Fedora 21 every day, without major issues. I'm not seeing any of the issues you describe. My Fedora is not a