Override job status

[Daniel L. Miller]

On 06/22/2010 09:50 PM, Daniel L. Miller wrote:
> I've been trying to tweak an upstart job script for ASSP - which is a
> perl script that has an option for forking.  Standard operation had no
> problems - but it was during the fork testing I ran into an issue.
>
> I used "expect fork" along with "respawn" - and I'm not certain what I
> did, but I wound up with multiple instances - upstart kept starting new
> ones.  I issued a stop, and then manually killed all the instances.  But
> now "status assp" shows "start/killed", with an invalid process id.  And
> attempt to start results in "Job already running" - though it is not.
>
> Is there any way I can tell upstart this job is in fact stopped - so I
> can start it again?  Running 0.6.3.
>    

Now running 0.6.5 - same problem.  The perl script contacts a call to 
fork() - I don't know what the appropriate manner to handle this within 
upstart should be - since I'm having very poor results using expect 
fork/daemon.

It works fine using the non-fork() call and without expect fork/daemon 
in the upstart script - but there's some behaviour in the perl script 
that works better when configured for the fork() operation.

-- 
Daniel