It was an error in that release of upstart that has been corrected. Classic sysvinit shutdown has behaved this way because that is how unix systems have always done it.
It was an error in that release of upstart that has been corrected. Classic sysvinit shutdown has behaved this way because that is how unix systems have always done it.