Upstart on an embedded target

[Scott James Remnant]

On Thu, 2007-02-01 at 12:15 -0600, Chemparathy, Cyril wrote:

> I have been working on getting upstart running on an embedded platform.
> Does anyone have any thoughts/comments on this in general?
> 
It should work well; though if you have very strict disk/flash or memory
requirements, you may want to look at eINIT instead.  Upstart still
relies on defining services and tasks as executables to be run, often
shell scripts -- which can be resource hungry.  With eINIT, you write
the tasks as C code embedded directly into the init system.

It all depends on the level of embeddedness, and customisability you
intend to have.  If the set of tasks and services can be changed, and
varies depending on configuration (e.g. OpenWRT) I'd recommend upstart.
If the services and tasks are fixed in stone, and resources are a
priority, eINIT may be better for you.

> Is Inotify a hard requirement for upstart? Since my platform does not
> include inotify support, we have put in some minor changes in cfgfile.c
> to take this out. Does anyone have any recommendations on how to do
> this cleanly probably by adding an option in the configure script?
> 
No; the fact that without inotify support, upstart doesn't read its
configuration files is a bug.

	https://bugs.launchpad.net/upstart/+bug/68904

If inotify support is not available, it should still read the
configuration; it will just require SIGHUP to force it to re-read the
config.  A fix for this will be in the next release.

Scott
-- 
Have you ever, ever felt like this?
Had strange things happen?  Are you going round the twist?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/upstart-devel/attachments/20070203/75c91f5d/attachment.pgp