On Wed, Sep 02, 2015 at 03:26:49PM -0000, Martin Pitt wrote:
> I still disagree that it's "undefined behaviour" -- if we have used the
> actual init.d script so far to start e. g. mysql under upstart,
That is *not* what we're doing. Installing the mysql-server-5.5 package on
trusty gives you:
$ ls -l /etc/rc?.d/*mysql* /etc/init.d/*mysql* /etc/init/*mysql*
ls: cannot access /etc/rc?.d/*mysql*: No such file or directory
-rwxr-xr-x 1 root root 5491 Feb 19 2014 /etc/init.d/mysql
-rw-r--r-- 1 root root 1770 Feb 19 2014 /etc/init/mysql.conf
$
This is the behavior for all packages using a current version of debhelper
to build.
Any packages that ship an upstart job and *do* have symlinks in /etc/rc?.d
for their matching init script are buggy and racy, and the change proposed
here will not make this problem worse.
On Wed, Sep 02, 2015 at 03:26:49PM -0000, Martin Pitt wrote:
> I still disagree that it's "undefined behaviour" -- if we have used the
> actual init.d script so far to start e. g. mysql under upstart,
That is *not* what we're doing. Installing the mysql-server-5.5 package on
trusty gives you:
$ ls -l /etc/rc?.d/*mysql* /etc/init.d/*mysql* /etc/init/*mysql* mysql.conf
ls: cannot access /etc/rc?.d/*mysql*: No such file or directory
-rwxr-xr-x 1 root root 5491 Feb 19 2014 /etc/init.d/mysql
-rw-r--r-- 1 root root 1770 Feb 19 2014 /etc/init/
$
This is the behavior for all packages using a current version of debhelper
to build.
Any packages that ship an upstart job and *do* have symlinks in /etc/rc?.d
for their matching init script are buggy and racy, and the change proposed
here will not make this problem worse.