init: new jobs should be automatically started

Reported by Vadim Smelyansky on 2008-12-13
2
Affects Status Importance Assigned to Milestone
upstart
Wishlist
Unassigned

Bug Description

Upstart is incompatible with sys V init
upstart must start job after configuration reload (kill -1 1) if it have 'start on runlevel <current runlevel>' in job file
example:
I add a new job for mgetty to answer modem like:
-----mgetty-fax-------
description "make mgetty answering modem for incoming fax calls at night"
start on runlevel [2345]
stop on runlevel [016]
instance
exec /sbin/mgetty ttyACM0 -F -n 1 -I VadiAz
respawn
------------------------------
Which means that this job should run while current runlevel one of [2345]
Reloading config (kill -1 1) do nothing and
initctl list show
mgetty-fax (waiting)

Waiting for what? current runlevel is 5 so why I must manually kick a job?

 status confirmed
 importance wishlist

Upstart is not intended to be compatible with sysvinit, only with the
sysv-rc interface that most people use with it.

That being said, we do need a facility for a job to be automatically
started on creation if the conditions for it are already true.

Scott
--
Scott James Remnant
<email address hidden>

Changed in upstart:
importance: Undecided → Wishlist
status: New → Confirmed
Changed in upstart:
milestone: none → 0.10
Changed in upstart:
milestone: 0.10 → none
status: Confirmed → Triaged
summary: - upstart must start job after config reload (kill -1 1) if it have start
- on runlevel <current runlevel>
+ init: new jobs should be automatically started
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers