supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: "Charles M. Gerungan" <charles@nednieuws.com>
Subject: Re: dnscache runs under daemontools, unable to bind (access denied) using runit
Date: Fri, 20 May 2005 19:18:56 +0200	[thread overview]
Message-ID: <2EF613DA-4D3C-434C-9E67-80CBBCA76E30@nednieuws.com> (raw)
In-Reply-To: <001f01c55d55$786c6460$6601a8c0@GHDESK>

Op 20-mei-2005, om 18:03 heeft Gregg Howe het volgende geschreven:

> 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.

Oh, man, I think it's time to modify the manpage as -- at least to me  
-- what you said wasn't obvious:

OPTIONS
        -u user[:group]
               setuidgid.   Set uid and gid to the user's uid and  
gid.  If user
               is followed by a colon and a group, set the gid to   
group's  gid
               instead of user's gid.  All supplementary groups are  
removed.

        -U user[:group]
               envuidgid.   Set  the environment variables $UID and  
$GID to the
               user's uid and gid.  If user is followed by a colon  
and a group,
               set $GID to the group's gid instead of user's gid.

So the difference is that -u drops privileges before the program is  
invoked and -U after?

Thanks for your help. Next step: tinydns.

-- 
Regards, Charles.



  reply	other threads:[~2005-05-20 17:18 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
2005-05-20 17:18   ` Charles M. Gerungan [this message]
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=2EF613DA-4D3C-434C-9E67-80CBBCA76E30@nednieuws.com \
    --to=charles@nednieuws.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).