From: GitHub <noreply@github.com>
To: cerowrt-commits@lists.bufferbloat.net
Subject: [dtaht/ceropackages] bab01a: Make named + dnssec startup mildly more robust.
Date: Sat, 14 Apr 2012 12:40:35 -0700 [thread overview]
Message-ID: <4f89d2b3b693a_2a931a01ae4796c3@sh2.rs.github.com.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 651 bytes --]
Branch: refs/heads/master
Home: https://github.com/dtaht/ceropackages
Commit: bab01a5fbb7af5c105ae74bc10b4aee890215894
https://github.com/dtaht/ceropackages/commit/bab01a5fbb7af5c105ae74bc10b4aee890215894
Author: Dave Taht <dave.taht@bufferbloat.net>
Date: 2012-04-14 (Sat, 14 Apr 2012)
Changed paths:
M net/bind-latest/files/named.init
Log Message:
-----------
Make named + dnssec startup mildly more robust.
If this doesn't work more of the time, I'm disabling dnssec entirely.
It turned out that most of my problems are on first boot,
where you are still rewriting flash and you can't save certain conf
files
reply other threads:[~2012-04-14 19:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4f89d2b3b693a_2a931a01ae4796c3@sh2.rs.github.com.mail \
--to=noreply@github.com \
--cc=cerowrt-commits@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox