From: Samuli Suominen <ssuominen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] rfc: use of the /run directory
Date: Wed, 18 May 2011 17:51:05 +0300 [thread overview]
Message-ID: <4DD3DCD9.8050203@gentoo.org> (raw)
In-Reply-To: <20110518144544.GA6260@bimsstein>
On 05/18/2011 05:45 PM, Henry Gebhardt wrote:
> On Wed, May 18, 2011 at 08:49:19AM +0300, Eray Aslan wrote:
>> On Wed, May 18, 2011 at 03:36:48AM +0200, Jeroen Roovers wrote:
>>> wrt /var/run on tmpfs, I recall packages installing daemons that expect
>>> their specific directories to be present in /var/run, and that do not
>>> play nice when that directory turns out empty, but we should be able to
>>> work around that by creating the directory in the init.d script before
>>> we execute the daemon.
>>
>> Yes. Some examples:
>>
>> https://bugs.gentoo.org/show_bug.cgi?id=332633
>> https://bugs.gentoo.org/show_bug.cgi?id=334245
>> https://bugs.gentoo.org/show_bug.cgi?id=334437
>> https://bugs.gentoo.org/show_bug.cgi?id=342049
>> https://bugs.gentoo.org/show_bug.cgi?id=333783
>>
>
> I thought I'd mention, the way systemd handles this is with an extra
> service and configuration files in /etc/tmpfiles.d [1]. I am sure OpenRC
> could use the same tool[2] for that.
>
> [1] http://0pointer.de/public/systemd-man/tmpfiles.d.html
> [2] http://0pointer.de/public/systemd-man/systemd-tmpfiles.html
Not all packages using /var/run own a init script, nor need one. Take
sys-fs/udisks[1] for example. Then, we need something to create these
dirs in OpenRC (or fix the package, but that might take some time...)
[1] http://bugs.gentoo.org/333893
next prev parent reply other threads:[~2011-05-18 14:53 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 16:57 [gentoo-dev] rfc: use of the /run directory William Hubbs
2011-05-17 18:11 ` Peter Volkov
2011-05-17 18:28 ` Nirbheek Chauhan
2011-05-17 18:43 ` Ângelo Arrifano
2011-05-17 18:50 ` Nirbheek Chauhan
2011-05-17 19:11 ` Peter Volkov
2011-05-17 19:20 ` Ângelo Arrifano
2011-05-17 19:07 ` William Hubbs
2011-05-17 20:35 ` James Cloos
2011-05-17 20:40 ` Markos Chandras
2011-05-18 0:06 ` James Cloos
2011-05-18 0:43 ` William Hubbs
2011-05-17 19:20 ` Panagiotis Christopoulos
2011-05-17 19:46 ` William Hubbs
2011-05-18 1:31 ` [gentoo-dev] " Duncan
2011-05-18 1:36 ` [gentoo-dev] " Jeroen Roovers
2011-05-18 5:49 ` Eray Aslan
2011-05-18 14:45 ` Henry Gebhardt
2011-05-18 14:51 ` Samuli Suominen [this message]
2011-05-18 15:02 ` [gentoo-dev] " Jonathan Callen
2011-05-17 19:48 ` [gentoo-dev] " Nirbheek Chauhan
2011-05-17 20:00 ` Olivier Crête
2011-05-17 20:07 ` Michał Górny
2011-05-17 20:11 ` Amadeusz Żołnowski
2011-05-17 20:23 ` Rich Freeman
2011-05-17 20:20 ` Panagiotis Christopoulos
2011-05-17 20:28 ` Michał Górny
2011-05-17 20:54 ` Olivier Crête
2011-05-17 21:00 ` Nirbheek Chauhan
2011-05-17 22:26 ` Drake Wyrm
2011-05-17 22:36 ` Marc Schiffbauer
2011-05-17 22:46 ` Nirbheek Chauhan
2011-05-18 0:06 ` William Hubbs
2011-05-17 22:50 ` Ciaran McCreesh
2011-05-18 0:12 ` William Hubbs
2011-05-23 6:30 ` Ciaran McCreesh
2011-05-23 7:05 ` Nirbheek Chauhan
2011-05-23 7:11 ` Ciaran McCreesh
2011-05-23 7:13 ` Michał Górny
2011-05-23 8:30 ` Nirbheek Chauhan
2011-05-20 8:58 ` Luca Barbato
2011-05-20 16:54 ` Mike Pagano
2011-05-22 19:13 ` Luca Barbato
2011-05-22 21:12 ` Ondřej Súkup
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=4DD3DCD9.8050203@gentoo.org \
--to=ssuominen@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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