From: Auke Booij <auke@tulcod.com>
To: gentoo-soc@lists.gentoo.org
Subject: Re: [gentoo-soc] Two ideas: R package installer (CRAN) and per-user daemons
Date: Fri, 19 Mar 2010 22:19:03 +0100 [thread overview]
Message-ID: <8f234f341003191419xe19b429h6a5d6af946548958@mail.gmail.com> (raw)
In-Reply-To: <4BA35E58.7030309@gentoo.org>
Petteri,
Thanks, there are indeed some solutions for users running X, but I
think a lot of services could benefit from being able to be started
without the user logging in (for example, webservers really should
launch clients' websites as fastcgi services at boot time) and without
having to run X anywhere.
As for who should handle this... there are some other ideas on the
ideas page concerning OpenRC, which I think is the most appropriate
project for this idea. And depending on the exact implementation, it
might very well be dependent upon the system's init.d software (in
this case OpenRC, but different distros use different systems). Ergo,
I'd say this idea does fit inside Gentoo's scope.
Auke.
On Fri, Mar 19, 2010 at 12:22 PM, Petteri Räty <betelgeuse@gentoo.org> wrote:
> On 18.3.2010 16.58, Auke Booij wrote:
>
>> 2. Per-user daemons. Currently, there are some daemons, like
>> PulseAudio, jackd, several download daemons, and soon possibly X.org
>> (which will no longer need to run as root, and really should run as a
>> normal user), which run as specific users, instead of root or a
>> systemwide daemon-specific user. There is currently no framework for
>> launching these daemons at all, and the current solution is to either
>> make users figure out their own solution (a popular one is an extra
>> line in .xinitrc), or to set the username in some conf.d file, thus
>> disabling the possibility to run several of them for different users.
>> I would like to develop an extension to our current init.d system
>> which will enable users to write and start their own init scripts,
>> which at first only run as themselves, not as another user. This would
>> make it possible to cleanly launch several identical daemons for
>> several users. This project would involve either writing a new
>> additional init.d system, or extend our current system. I would like
>> to know 1. if you guys are understanding a word of what I'm saying at
>> all 2. if this would be an interesting idea (I think it is, of course)
>> 3. anyone has any ideas or would like to mentor me.
>>
>
> Isn't this something that should be handled by the upstream projects
> instead of doing it at the distribution level? Also see:
> http://standards.freedesktop.org/autostart-spec/autostart-spec-latest.html
>
> Regards,
> Petteri
>
>
next prev parent reply other threads:[~2010-03-19 21:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 14:58 [gentoo-soc] Two ideas: R package installer (CRAN) and per-user daemons Auke Booij
2010-03-19 11:22 ` Petteri Räty
2010-03-19 21:19 ` Auke Booij [this message]
2010-03-19 16:46 ` [gentoo-soc] " Sébastien Fabbro
2010-03-19 21:27 ` Auke Booij
2010-03-19 22:10 ` Sébastien Fabbro
2010-03-22 13:33 ` Auke Booij
2010-03-28 18:28 ` Hans de Graaff
2010-03-26 15:25 ` Auke Booij
2010-04-03 14:27 ` Auke Booij
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=8f234f341003191419xe19b429h6a5d6af946548958@mail.gmail.com \
--to=auke@tulcod.com \
--cc=gentoo-soc@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