[Bug 1278529] Re: Using S3, BackendException: No connection to backend

** Also affects: python-boto (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-boto in Ubuntu. https://bugs.launchpad.net/bugs/1278529 Title: Using S3, BackendException: No

[Bug 1521771] [NEW] init.d.mysql shutdown timeout value does not match init/mysql.conf value

Public bug reported: In `/etc/init/mysql.conf`, the configuration is set to wait 5 minutes after a SIGTERM is issued before a SIGKILL is issued. The value was intentionally set that high because sometimes the default of 5 seconds wasn't long enough [1]. 1.

[Bug 1273462] Re: Users can mistakenly run init.d scripts and cause problems if an equivalent upstart job already exists

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

Re: [Bug 1521771] Re: init.d.mysql shutdown timeout value does not match init/mysql.conf value

Thanks for the reply. For the mysql-5.6 package, I recommend clearly out the "init.d" script except for the redirect to the "upstart" script. This will avoid the false impression that the code in in the "init.d" script is still active. Mark -- You received this bug notification