Comment 8 for bug 448095

I'm having difficulty understanding what this script accomplishes. If it it co-exists with the existing init script, then when '/etc/init.d/resolvconf start' does finally run, ${RUNDIR}/interface will be deleted again, which is not what we wanted.

If it's meant to act as a replacement for the start action of the init script, then it at also needs to perform the "update -i" action the original init script does to initialise all the things that listen to resolvconf updates.

I believe Scott was hoping that someone would port the entire resolvconf init script to upstart. In the resolvconf model (I believe) a service restart is considered to merely be a stop followed by a start. The problem with the resolvconf init script is that it makes a distinction between a boot-time start and a restart. Resolvconf will delete the contents of the interface directory on a boot-time start, but not on a restart. I think how to distinguish between the two is a question for the upstart developers as I think it's a requirement that exists outside their current use-cases. Someone please correct me if I'm wrong about this.