<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3314" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><SPAN class=484001417-31072008><FONT face=Arial size=2>A job has many
attributes like restartability, resource limitations, and I am sure this
will grow over time.</FONT></SPAN></DIV>
<DIV><SPAN class=484001417-31072008><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=484001417-31072008><FONT face=Arial size=2>Right now, once a
job is defined the way to update it is to update the job file and Upstart will
reload it.</FONT></SPAN></DIV>
<DIV><SPAN class=484001417-31072008><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=484001417-31072008><FONT face=Arial size=2>I was wondering
about the following questions, </FONT></SPAN></DIV>
<DIV><SPAN class=484001417-31072008><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=484001417-31072008><FONT face=Arial size=2>1. When a job file
gets updated and reloaded, how does it affect the behavior of existing instances
of the job. Say I modified the restartability field and disable restarts. Will
it affect the job instance that was started before the job file modification?
How is the new job file, related to what used to be.</FONT></SPAN></DIV>
<DIV><SPAN class=484001417-31072008><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=484001417-31072008><FONT face=Arial size=2>2. Would it make
sense to have D-Bus client API change modify some of the attributes of a
job or job instance in memory without modifying the job file on
disk?</FONT></SPAN></DIV>
<DIV><SPAN class=484001417-31072008><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=484001417-31072008><FONT face=Arial size=2>These questions come
up when trying to figure out how to bridge System
Management/Configuration affect job files, jobs or job
instances.</FONT></SPAN></DIV>
<DIV><SPAN class=484001417-31072008></SPAN> </DIV>
<DIV><SPAN class=484001417-31072008><FONT face=Arial size=2>Many of the job
files will never be affected by configuration. But I suspect there will be a
class of jobs that may have an initial definition during installation but may be
affected by configuration. </FONT></SPAN></DIV>
<DIV><SPAN class=484001417-31072008><FONT face=Arial size=2>
Some of these changes may be temporary in that it may not survive a system
restart and some of these configurations may be saved and might need to survive
a system restart.</FONT></SPAN></DIV>
<DIV><SPAN class=484001417-31072008> </SPAN></DIV>
<DIV><SPAN class=484001417-31072008><FONT face=Arial size=2>How do we do
this? I have some thoughts/options on how these could be done. But I wanted
to check if this has been discussed before and what the community is
thinking. </FONT> </SPAN></DIV>
<DIV><SPAN class=484001417-31072008><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=484001417-31072008><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=484001417-31072008><FONT face=Arial
size=2>Sari</FONT></SPAN></DIV></BODY></HTML>