From: lanek@novenine.com
To: supervision@list.skarnet.org
Cc: "Charlie Brady" <charlieb-supervision@budge.apana.org.au>
Subject: Re: Installing dnscache with runit, without other djb utils
Date: Sun, 20 Jul 2008 01:15:35 +0700 (WIT) [thread overview]
Message-ID: <37937.125.162.57.235.1216491335.squirrel@novenine.com> (raw)
> What more detail are you looking for?
>
> The seed file is only useful if it is attached to standard input of the
> dnscache process, which will read up to 128 bytes to seed its RNG.
[d]nscache reads a seed, up to 128 bytes, from standard input, and passes
the seed to dns_random_init^1
Yes, dnscache reading the seed from _standard input_ details better the
situation:
exec<seed or dnscache <seed
become more intelligible. ("If it's a cow don't call it a bovine," says
Ledgard.)
Thank you _very much_ for the vital correction, I don't know how I have
missed
that ... eventually it has been, if I remember correctly, a mere mapping
operation--from daemontools to runit ... And was thinking you were hinting at
some synchronization problems.
/Roy Lanek
1. Configuration, http://cr.yp.to/djbdns/dnscache.html
--
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS malu bertanya, sesat di jalan
SSSSS . s l a c k w a r e SSSSSS embarrassed to ask will result in
SSSSS +------------ linux SSSSSS getting lost
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
next reply other threads:[~2008-07-19 18:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-19 18:15 lanek [this message]
[not found] <49351.125.162.61.255.1216395759.squirrel@novenine.com>
2008-07-19 16:24 ` Charlie Brady
-- strict thread matches above, loose matches on Subject: below --
2008-07-19 6:02 lanek
2006-09-28 0:12 Roy Lanek
2008-07-18 14:20 ` Charlie Brady
2006-09-20 22:30 Lloyd Zusman
2006-09-20 23:49 ` Wayne Marshall
2006-09-21 0:07 ` Vincent Danen
2006-09-21 0:12 ` Charlie Brady
2006-09-21 0:44 ` Lloyd Zusman
2006-09-21 1:03 ` Charlie Brady
2006-09-21 1:28 ` Lloyd Zusman
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=37937.125.162.57.235.1216491335.squirrel@novenine.com \
--to=lanek@novenine.com \
--cc=charlieb-supervision@budge.apana.org.au \
--cc=supervision@list.skarnet.org \
/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;
as well as URLs for NNTP newsgroup(s).