[cros-dev] systemd

19 views
Skip to first unread message

Nasser Grainawi

unread,
May 3, 2010, 4:03:10 PM5/3/10
to Chromium OS dev
Has anyone looked at systemd as an Upstart replacement? Seems ideal for
the boot time requirements of Chromium OS.

http://0pointer.de/blog/projects/systemd.html
(There's a section on Upstart a quarter of the way down the page)

Nasser

--
Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en

Chris Masone

unread,
May 3, 2010, 5:17:11 PM5/3/10
to Nasser Grainawi, Chromium OS dev
Seems like a great thing to look into after version 1 :-)

tedbo

unread,
May 3, 2010, 5:45:28 PM5/3/10
to Chris Masone, Nasser Grainawi, Chromium OS dev
On Mon, May 3, 2010 at 2:17 PM, Chris Masone <cma...@chromium.org> wrote:
> Seems like a great thing to look into after version 1 :-)

I've read the posting but haven't tried it out yet. I agree that it
would be too disruptive in the short term, especially since I'm not
sure that it would pay off in terms of boot speed. Upstart is working
pretty well for us. It is stable and lets us control the boot sequence
so that we can start critical stuff in parallel and defer other
services to when the system is expected to be a bit more idle.

That said, I do tend to prefer the launchd model and our Upstart jobs
continue to become more complicated to reason about. In addition I
like that they are considering systemd as a session manager as well.
Right now we are abusing some features of Upstart to partially use it
as a session manager and that doesn't feel right to me.

ted

Will Drewry

unread,
May 3, 2010, 5:54:43 PM5/3/10
to tedbo, Chris Masone, Nasser Grainawi, Chromium OS dev
On Mon, May 3, 2010 at 4:45 PM, tedbo <te...@chromium.org> wrote:
> On Mon, May 3, 2010 at 2:17 PM, Chris Masone <cma...@chromium.org> wrote:
>> Seems like a great thing to look into after version 1 :-)
>
> I've read the posting but haven't tried it out yet. I agree that it
> would be too disruptive in the short term, especially since I'm not
> sure that it would pay off in terms of boot speed. Upstart is working
> pretty well for us. It is stable and lets us control the boot sequence
> so that we can start critical stuff in parallel and defer other
> services to when the system is expected to be a bit more idle.
>
> That said, I do tend to prefer the launchd model and our Upstart jobs
> continue to become more complicated to reason about. In addition I
> like that they are considering systemd as a session manager as well.
> Right now we are abusing some features of Upstart to partially use it
> as a session manager and that doesn't feel right to me.

As a bonus, systemd also deals with many of the features in or
targeted for minijail. It also avoids the ptrace() hackery for daemon
tracking. :)

Definitely worth checking out in the future, imo,
will
Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages