ALT Linux Team development discussions
 help / color / mirror / Atom feed
From: Igor Homyakov <homyakov@ramax.spb.ru>
To: ALT Linux Team <devel@altlinux.ru>
Subject: [devel] Q: sockd pid file
Date: Wed, 16 Oct 2002 14:04:59 +0400
Message-ID: <20021016100459.GA8655@kadath.pm.ramax.spb.ru> (raw)

[-- Attachment #1: Type: text/plain, Size: 561 bytes --]

Привет !

C dante (socks proxy) есть проблема при создании pid файла.
Есть 2 ключевых пользователя привилегированный (sockd) и 
не привилегированный (nobody). Предполагаеться, что от имени
первого происходит создание сокета, getpwname, работа с PAM
и почему-то создание pid файла. Всё остальное удел nobody.

из-за этого получаеться что не хватает прав для записи в /var/run

моя беседа с разработчиками прилагаеться.

Вопрос: как правилнее поступить, патчит или создавать pid файл
        как предлагает Michael ?
	
--
Igor Homyakov
<homyakov AT ramax.spb.ru>

[-- Attachment #2: Type: message/rfc822, Size: 1617 bytes --]

From: Michael Shuldman <michaels@inet.no>
To: Igor Homyakov <homyakov@ramax.spb.ru>
Subject: Re: sockd pid file
Date: Wed, 16 Oct 2002 11:58:43 +0200
Message-ID: <20021016115843.23708@bastesen.inet.no>

Igor Homyakov wrote,
> On Tue, Oct 15, 2002 at 11:54:15AM +0200, Michael Shuldman wrote:
> > > Q: Why sockd does not wrote pid file BEFORE droping privileges ?
> > > ( in serverinit() function or immediatly after )
> 
> There will be no access problems to /var/run if sockd creates
> /var/run/sockd.pid while running as root (like most other daemons do).

sockd starts using the privileges given in sockd.conf as soon as
possible.  You can create the file yourself and make it writable
by sockd if that is a problem for you.


-- 
  _ // 
  \X/ -- Michael Shuldman <michaels@inet.no>



             reply	other threads:[~2002-10-16 10:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-16 10:04 Igor Homyakov [this message]
2002-10-16 11:05 ` Dmitry V. Levin
2002-10-16 10:58   ` Igor Homyakov
2002-10-16 12:07     ` Dmitry V. Levin
2002-10-16 12:16       ` Igor Homyakov

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=20021016100459.GA8655@kadath.pm.ramax.spb.ru \
    --to=homyakov@ramax.spb.ru \
    --cc=devel@altlinux.ru \
    /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

ALT Linux Team development discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
		devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
	public-inbox-index devel

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git