[Buildroot] Init and Supervisor start. Help please.

Thomas Petazzoni thomas.petazzoni at free-electrons.com
Tue Nov 18 15:16:09 UTC 2014


Dear Lennart Ramberg,

On Tue, 18 Nov 2014 15:01:38 +0100, Lennart Ramberg wrote:

> How should supervisor be automatically started?
> Is the below way to go (kiosk mode) in principle right?
> 
> /boot/grub/grub.cfg:
> 
> set default="0"
> set timeout="5"
> 
> menuentry "Buildroot" {
>     linux /bzImage root=/dev/sda1 init=/usr/bin/supervisord
> }
> 
> Setting init=/myprogram worked as expected. But but experimenting
> with letting supervisord start myprogram just caused kernel panic,
> so maybe I'm heading the wrong way?

Reading from http://supervisord.org/:

"""
It shares some of the same goals of programs like launchd, daemontools,
and runit. Unlike some of these programs, it is not meant to be run as
a substitute for init as “process id 1”. Instead it is meant to be used
to control processes related to a project or a customer, and is meant
to start like any other program at boot time.
"""

So using supervisord as init doesn't seem to be the right thing to do.
Instead, use another init (whichever you want), and then use
supervisord to start/monitor your daemons/system services.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com



More information about the buildroot mailing list