Linux Today: Linux News On Internet Time.
Search Linux Today
search.internet.com
Linux News Sections:  Blog -  Developer -  High Performance -  Infrastructure -  IT Management -  Security -  Storage -
Linux Today Navigation
LT Home
Preferences
Contribute
Link to Us
Search
Linux Jobs

Become a Marketplace Partner

internet.commerce
Be a Commerce Partner














The Linux Channel at internet.com
Linux Today
Enterprise Linux Today
Apache Today
JustLinux.com
Linux Planet
PHPBuilder
All Linux Devices
Technology Jobs

JustTechJobs.com

LinuxToday Newsletters
Subscribe News
Subscribe PR
Subscribe Security

internet.com
IT
Developer
Internet News
Small Business
Personal Technology

Search internet.com
Advertise
Corporate Info
Newsletters
Tech Jobs
E-mail Offers

 







Current Newswire:

Linux can compete with the iPad on price, but where’s the magic?

The Bruno Knaapen Technology Learning Center is Established

Anjal: GNOME's Evolution for Netbooks

Linux Mint 8 KDE Community Edition

Open source means freedom from 'anti-features'

GTalX - Google Voice Chat has arrived in Ubuntu 9.10 (Karmic)

Top 10 Super Bowl tech ads

OOXML not suitable for Norwegian government, says study

Add Cloud Storage to OpenOffice.org with SMECloud

10 Ways that Enterprises use Linux




Senior Linux Administrator - Red Hat (IL)
Next Step Systems
US-IL-Chicago

Justtechjobs.com Post A Job | Post A Resume
:Controlling Ubuntu's and Fedora's Upstart (the init replacement)
Controlling Ubuntu's and Fedora's Upstart (the init replacement)
May 13, 2009, 22 :33 UTC (0 Talkback[s]) (3633 reads)

(Other stories by Juliet Kemp)

"But what about setting up a particular job for yourself? You keep your job definitions in /etc/init/jobs.d, and they should be plain text files, and not executable. Your job needs to have either an exec line:

exec /bin/echo "ping"

"giving a path to a binary, and the arguments to pass to it; or a script section, as in the runlevel 3 job description above, which has a shell script to be run with /bin/sh. These define what will be run when the job is triggered. Jobs can be set to respawn with the line:

respawn

"There's an automatic limit set to this: if a process is respawned more than 10 times within 5 seconds, it will be stopped and not restarted. You can alter this default with:

respawn limit 20 5"

Complete Story

Related Stories:
A Peek at DeviceKit in Fedora 11 and Beyond(May 07, 2009)
What You Should Expect from Fedora 11(May 07, 2009)
Ubuntu and Fedora Replace init with Upstart(May 04, 2009)
How to build a boot server(Apr 15, 2009)
The Linux Boot Process(Apr 14, 2009)
How does Ubuntu's Upstart system initialization compare with runit?(Mar 17, 2009)
Taming Your Daemons With PSMon(Sep 02, 2008)
Ubuntu's Upstart Event-Based init Daemon(Feb 11, 2008)



No talkbacks posted.
  Home | Search Talkbacks | Customize View    Top of Page  



Enter your comments below:

* Your Name:

* Your Email Address:

* Subject:

CC: [will also send this talkback to an E-Mail address]

* Comments:

Tags allowed:<I>,<B> and <U>. See our talkback-policy for more about talkback content.

Fields marked with * are required!






..............................




All times are recorded in UTC.
Linux is a trademark of Linus Torvalds.
Powered by Linux, Apache and PHP


The Network for Technology Professionals

Search:

About Internet.com

Legal Notices, Licensing, Permissions, Privacy Policy.
Advertise | Newsletters | E-mail Offers