Any hints on how to write services for new upstart?

[Jonathan Kamens]

OK, so before the recent upstart upgrade, I had two services in 
/etc/event.d.

Apparently, /etc/event.d is now obsolete.  Any hints on what it has been 
replaced with and/or pointers to documentation on how to define services 
for the new and (presumably) improved upstart?

   jik

[Rahul Sundaram]

On 12/14/2009 08:39 AM, Jonathan Kamens wrote:
>  OK, so before the recent upstart upgrade, I had two services in
>  /etc/event.d.
>  
>  Apparently, /etc/event.d is now obsolete.  Any hints on what it has been
>  replaced with and/or pointers to documentation on how to define services
>  for the new and (presumably) improved upstart? 
The new location is /etc/init. The format has also changed. If you want
to convert, refer to

https://www.redhat.com/archives/fedora-devel-list/2009-December/msg00184....

The few existing packages should should serve as examples. The current
recommendation is start you continue to rely on sysv compatibility in
upstart rather than use upstart jobs since it is possible, the job
definitions might change again before we get to 1.0.

Rahul

[Bill Nottingham]

Jonathan Kamens (jik(a)kamens.brookline.ma.us) said: 
>  OK, so before the recent upstart upgrade, I had two services in
>  /etc/event.d.
>  
>  Apparently, /etc/event.d is now obsolete.  Any hints on what it has
>  been replaced with and/or pointers to documentation on how to define
>  services for the new and (presumably) improved upstart? 
Basic notes:

- Services go in /etc/init, and must end in .conf
- You can no longer have multiple 'start on' or 'stop on' stanzas;
combine
  them with 'and' or 'or'
- The default is for services to respawn. If you don't want that, mark
  it as 'task'

More info is in init(5) in the new upstart package.

Bill