Equivalent for the "pid file" stanza in newer versions of upstart

I'd like to be able to use upstart to manage daemons where I don't have complete control over the forking behaviour. The "pid" stanza is removed as of version 0.3.9, so I can't point it at a pid file. What is the correct way to go about this? Do I have to write a wrapper script that issues SIGSTOP?

Read this section of the Upstart Cookbook very carefully: http://upstart.ubuntu.com/cookbook/#expect

In a nutshell, if your daemon forks once, use "expect fork". If it truly daemonizes (double-forks), specify "expect daemon".

Does having a load balancer allow you to re-use socket connections?

How to set the default source (src) ip address when you have mulitple IP's on a virtual interface

Making ssh easier for our Windows user community

Which events specifically cause Windows 2008 to mark a SAN volume offline?

How can I run an application from a network share without prompting for Admin password?

OpenVPN failing on self-signed certificate over udp, works over tcp

How to make a variable in a parameterized Puppet class default to the value of another parameter?

Clearing Java certificates cache (force reload certificates)

What is the most efficient way to backup a directory full of large database backup files?

Nginx worker_processes and multi core cpu's - Do Hyper-threading cores count?