From: "Gregg Howe" <gregg@astronumerics.com>
Subject: Re: dnscache runs under daemontools, unable to bind (access denied) using runit
Date: Fri, 20 May 2005 09:03:31 -0700 [thread overview]
Message-ID: <001f01c55d55$786c6460$6601a8c0@GHDESK> (raw)
In-Reply-To: <41EB9410-E945-46D1-A17D-171BFC4750DF@nednieuws.com>
----- Original Message -----
From: "Charles M. Gerungan" <charles@nednieuws.com>
To: <supervision@list.skarnet.org>
Sent: Friday, May 20, 2005 5:04 AM
Subject: dnscache runs under daemontools, unable to bind
(access denied) using runit
> This starts up dnscache and it responds to queries:
>
> # cat run.daemontools
> #!/bin/sh
> exec 2>&1
> exec <seed
> exec envdir ./env sh -c '
> exec envuidgid Gdnscache softlimit -o250 -d
"$DATALIMIT" /usr/
> local/bin/dnscache
> '
>
> This does not start up (an adapted version of
http://www.skarnet.org:
> 80/lists/archive.cgi?2:msp:1046:midfmaimamejgmijfagg --
the content
> of the env dir wasn't given so I hope I interpreted the
manual
> correctly):
>
> # cat run
> #!/bin/sh
> exec 2>&1
> exec <seed
> exec chpst -v -u Gdnscache:Gnofiles -e ./env -o 250
/usr/local/bin/
> dnscache
>
> The error I'm getting when invoking:
>
> # ./run
> dnscache: fatal: unable to bind UDP socket: access denied
>
>
> Why am I getting the error and how do I solve it?
>
> --
> Regards, Charles.
Charles--
The "-u" option in chpst changes dnscache to an unprivileged
user before it executes, so it isn't able to bind the UPD
socket. If you use "-U" instead, dnscache will be able to
complete this before it changes to Gdnscache.
Gregg
next prev parent reply other threads:[~2005-05-20 16:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-20 12:04 Charles M. Gerungan
2005-05-20 12:10 ` Charles M. Gerungan
2005-05-20 16:03 ` Gregg Howe [this message]
2005-05-20 17:18 ` Charles M. Gerungan
2005-05-20 17:22 ` Charlie Brady
2005-05-20 17:31 ` Charles M. Gerungan
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='001f01c55d55$786c6460$6601a8c0@GHDESK' \
--to=gregg@astronumerics.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 NNTP newsgroup(s).