From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: net start named failed
Date: Fri, 15 Mar 2019 12:25:00 -0000 [thread overview]
Message-ID: <122edb59-e3f9-aad2-bd34-1fa1e25b4256@SystematicSw.ab.ca> (raw)
In-Reply-To: <1552405112191-0.post@n5.nabble.com>
On 2019-03-12 09:38, jwang wrote:
> googled a bit and tried: "/usr/sbin/named -f -g -S 256" but no joy
Have you installed cygrunsrv package to wrap and manage Unix daemons on Windows,
and read docs and FAQ on use. [bind should depend on cygrunsrv]
Have you run /usr/sbin/named-config elevated?
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-03-15 12:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 15:43 jwang
2019-03-12 15:44 ` jwang
2019-03-15 12:25 ` Brian Inglis [this message]
2019-03-15 12:32 ` jwang
2019-03-16 12:11 ` jwang
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=122edb59-e3f9-aad2-bd34-1fa1e25b4256@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).