This bug was fixed in the package lsb - 4.1+Debian11ubuntu6.1
---
lsb (4.1+Debian11ubuntu6.1) trusty; urgency=medium
* Add 01-upstart-lsb from the upstart package and make
executing rc.d scripts no-op if there is an upstart
job for that script. (LP: #1273462)
-- Zhang Hua
Both mysql-server-5.5 and mysql-server-5.6 packages (e.g. under Trusty
Thar) provide a sysvinit script and an upstart job for mysql. The
problem here is that the maintainer has a very strange approach:
1. The sysvinit script links are symply removed in the postinstall script using
update-rc.d
2.T
** Changed in: upstart (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273462
Title:
Users can mistakenly run init.d scripts and cause problems if an
equ
** Tags removed: scripts verification-done-trusty verification-needed
** Tags added: trusty verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273462
Title:
Users can mistakenly run in
On 3 December 2015 at 17:41, Mark Stosberg wrote:
> In Bug #1521771, I spent some time tracking down different behavior
> between the mysql-5.5 "init" and "upstart" scripts. They differ on how
> many seconds are waited between the SIGTERM and SIGKILL signals are
> sent. Different values can mean t
Marking as verified on Trusty since I was able to do more testing.
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273462
Title:
Users can mistakenly run init
In Bug #1521771, I spent some time tracking down different behavior
between the mysql-5.5 "init" and "upstart" scripts. They differ on how
many seconds are waited between the SIGTERM and SIGKILL signals are
sent. Different values can mean the difference between a slower clean
shutdown and a shutdow
** Changed in: lsb (Ubuntu)
Importance: Undecided => High
** Changed in: lsb (Ubuntu Utopic)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273462
Title:
Users c
** No longer affects: mysql-5.5 (Ubuntu)
** No longer affects: mysql-5.5 (Ubuntu Trusty)
** No longer affects: mysql-5.5 (Ubuntu Utopic)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273462
Title:
I couldn't find any regression in my testing but since it wasn't that
extensive, I'm not marking it a verified just yet.
I really like the behavior improvement. Now, a regular user has a convenient
way to check service statuses:
/etc/init.d/acpid status
Instead of the obtuse old way:
env -
** Branch linked: lp:ubuntu/trusty-proposed/lsb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273462
Title:
Users can mistakenly run init.d scripts and cause problems if an
equivalent upstart job
Hello Eric, or anyone else affected,
Accepted lsb into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lsb/4.1+Debian11ubuntu6.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki
I sponsored this a while ago, unsubscribing sponsors. This is in the
hands of the SRU team now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273462
Title:
Users can mistakenly run init.d scripts a
@Martin
Note that this is bug a regression - previously, before the (I presume)
dh_installinit change, /etc/init.d/foo was a symlink to /lib/init
/upstart-job so a user running /etc/init.d/foo by hand was redirected to
upstart anyway. So while I appreciate that a user might now be getting
desired
> No /etc/rc?.d/ links
Of course, but I thought the point here was that one could/would call
/etc/init.d/mysql directly when doing manual admin operations.
The first part of the patch, which disables an init.d script when called
through /etc/rc?.d/ is correct; if this happens (upstart job with rc
On Wed, Sep 02, 2015 at 03:26:49PM -, 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:
$
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, then
this does not sound either racy nor undefined; it surely isn't what we
*intended* to do, though?
My concern is, this fix will change behaviour for *all* pack
> Thus in trusty you don't have the option to use dependency-based
> sysvinit scripts, you *have* to have rc?.d symlinks; and they are
> being used through upstart too via /etc/init/rc.conf.
In that case, any /etc/rc?.d symlink that shadows an upstart job is
still going to be doing the wrong thing
Steve Langasek [2015-09-01 21:38 -]:
> The *only* thing that's made a no-op is the invocation of the init
> script *by the rc?.d symlink*. This is something that should never
> happen anyway; our dependency-based boot is already supposed to bypass
> invoking this script in favor of the upstart
> I think this should be the responsibility of existing packages to make
they are doing the correct thing.
That is not sufficient for an SRU. Your SRU needs to be compatible with
the existing packages in the archive /as they are/, not as you declare
they should be.
However, per my previous comme
I think the change description within the patch is wrong (or at least,
misleading/incomplete). What this patch actually does is:
- for anything that calls /etc/init.d/foo, if /etc/init/foo.conf exists, make
the call a passthrough to upstart instead of calling the init script.
- for anything th
With my SRU/TB hat on, I'd prefer making individual changes to e. g.
mysql and other packages rather than changing this wholesale. Even if we
did review all packages in Ubuntu which ship an init script that still
leaves third-party scripts (and there are a lot of them). So I strongly
recommend not
Chris,
Could you review [Regression Potential] section I updated just now ?
I think this should be the responsibility of existing packages to make they
are doing the correct thing. This change in lsb should be in the right road,
and the same change has also landed into Utopic, so this chan
** Description changed:
[ impact ]
Previously, init.d scripts that were replaced by upstart jobs had
"upstart-job" symlink as a redirect in-place, which directed users at
using upstart commands. Despite the good intentions, that never actually
taught people about the correct interface
I'd like to see more thought in the Regression Potential section,
because it clearly is NOT 'None'.
Please search though and check if any existing packages call
/etc/init.d/ either through any maintscripts, or if any
other scripts will call /etc/init.d/. For each of these
ensure that a 'No-op' is
Updated patch with bug number and version changed.
** Patch added: "fix-lp1273462-trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1273462/+attachment/4440531/+files/fix-lp1273462-trusty.debdiff
** Description changed:
[ impact ]
Previously, init.d scripts that
Updated patch with bug number and version changed.
** Patch added: "fix-lp1273462-trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1273462/+attachment/4440530/+files/fix-lp1273462-trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Hi Hua,
Thanks for the patch, I can confirm that this patch fixed the issues I had with
MySQL.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273462
Title:
Users can mistakenly run init.d scripts a
** Changed in: lsb (Ubuntu Trusty)
Assignee: Dimitri John Ledkov (xnox) => Hua Zhang (zhhuabj)
** Changed in: lsb (Ubuntu Trusty)
Status: Confirmed => In Progress
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Patch removed: "trusty_v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1273462/+attachment/4430332/+files/trusty_v2.debdiff
** Patch removed: "trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1273462/+attachment/4428923/+files/trusty.debdiff
** Description changed:
[ impact ]
Previously, init.d scripts that were replaced by upstart jobs had
"upstart-job" symlink as a redirect in-place, which directed users at
using upstart commands. Despite the good intentions, that never actually
taught people about the correct interface
@Edward,
I tested above trusty.debdiff, but I found the constraint "Replaces:
upstart (<< 1.12.1-0ubuntu8) && Breaks: upstart (<< 1.12.1-0ubuntu8)" prevents
installing lsb-base package. error logs pls refer the link [1], so I remove
them. I will upload trusty_v2.debdiff.
Then I buil
** Patch added: "trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1273462/+attachment/4428923/+files/trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273462
Title:
@zhhuabj read my comment
https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1273462/comments/6
I have correct the status and the location of where the fix needs to be
backported to, without changing the effective status. In utopic the bug
was fixed in upstart, but in trusty it needs to be fix
Hi Dimtri,
Why it can be fixed for utopic but not trusty, they both still use upstart
by default.. right ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273462
Title:
Users can mistakenly run
Hi, any progress/update for this ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273462
Title:
Users can mistakenly run init.d scripts and cause problems if an
equivalent upstart job already exi
If a "stop" on the mysql init script does not work, the init script
should be removed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273462
Title:
Users can mistakenly run init.d scripts and cause
upstart init-functions.d hook has ended up being shipped by lsb, since
circular dependencies onto upstart from sysv are a bad idea. Hence re-
assigning SRU to lsb.
** Changed in: upstart (Ubuntu Trusty)
Status: Triaged => Won't Fix
** Also affects: lsb (Ubuntu)
Importance: Undecided
** Branch linked: lp:ubuntu/trusty/upstart
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273462
Title:
Users can mistakenly run init.d scripts and cause problems if an
equivalent upstart job alre
This bug was fixed in the package upstart - 1.12.1-0ubuntu6
---
upstart (1.12.1-0ubuntu6) utopic; urgency=medium
* Map force-reload to restart command in init-functions hook.
* Use variable expansion, instead of basename as that is shipped in
/usr.
* Resolve test-failure, wh
** Changed in: upstart (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273462
Title:
Users can mistakenly run init.d scripts and cause problems if an
equivale
** Description changed:
+ [ impact ]
+
+ Previously, init.d scripts that were replaced by upstart jobs had
+ "upstart-job" symlink as a redirect in-place, which directed users at
+ using upstart commands. Despite the good intentions, that never actually
+ taught people about the correct interface
** Also affects: upstart (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: mysql-5.5 (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: upstart (Ubuntu Utopic)
Importance: Critical
Assignee: Dimitri John Ledkov (xnox)
Status: Tri
Please take a look at
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1072518 and let us
know if this is the same issue or not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273462
Title:
Users
lsb -> upstart, because upstart will just provide lsb integration
snippet
** Changed in: lsb (Ubuntu)
Importance: Undecided => Critical
** Changed in: lsb (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Package changed: lsb (Ubuntu) => upstart (Ubuntu)
--
You received
45 matches
Mail list logo
