** No longer affects: upstart (Ubuntu Lucid)
** No longer affects: upstart (Ubuntu Maverick)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/94065
Title:
init: add non-destructive means to disable a
What is the wrap up of the fix now?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/94065
Title:
init: add non-destructive means to disable a job
To manage notifications about this bug go to:
Excerpts from Andy Hauser's message of Fri Jun 17 08:31:38 UTC 2011:
What is the wrap up of the fix now?
You can stop job from automatically starting with
sudo sh -c 'echo manual /etc/init/job.override'
--
You received this bug notification because you are subscribed to upstart
.
** Changed in: upstart
Status: In Progress = 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/94065
Title:
init: add non-destructive means to disable a job
To manage notifications
Nominating for SRU:
The moving of core system daemons (ie - mysql, libvirt-bin, etc) to
Upstart without the means for non-destructive disabling impairs the
ability to use those services on servers, particularly in clustered
environments. This is a regression.
The addition of the 'manual'
Assuming I don't have permission to set the appropriate flags here -
can't see the options described in the SRU document.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/94065
Title:
init: add
pdf: in order to set SRU flags, I think you have to look at the bug from the
Ubuntu POV ... check that the URL is of the form /ubuntu/source/+upstart/..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Excerpts from pdf's message of Mon Apr 04 12:56:26 UTC 2011:
Nominating for SRU:
The moving of core system daemons (ie - mysql, libvirt-bin, etc) to
Upstart without the means for non-destructive disabling impairs the
ability to use those services on servers, particularly in clustered
On 05/04/11 05:04, Clint Byrum wrote:
I'm not totally against this for SRU, but I would like to make sure we are
sure that it is entirely necessary before going forward.
Understood.
First, I would like to refute the statement that it is impossible.
This can be achieved on a script-specific
** Changed in: upstart
Status: In Progress = 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/94065
Title:
init: add non-destructive means to disable a job
--
ubuntu-bugs mailing
Please don't change upstream tasks to Fix Committed unless the code is
in trunk (lp:upstart) or Fix Released unless the code is in a released
tarball.
To track changes to Upstart in Natty, add an Ubuntu Task to the bug.
** Changed in: upstart
Status: Fix Released = In Progress
--
You
Would I be likely to garner any traction in nominating this for SRU,
considering the impact for server and cluster environments (and the fact
that core services like MySQL are on upstart)
Seconded. This is a critical feature, imo...
--
You received this bug notification because you are a
Rolling back to In Progress since this hasn't actually landed in trunk
yet
** Changed in: upstart
Status: Fix Committed = Triaged
** Changed in: upstart
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Would I be likely to garner any traction in nominating this for SRU,
considering the impact for server and cluster environments (and the fact
that core services like MySQL are on upstart), the majority of which
will be using LTS? Or at the very minimum, a backport? Judging from
the attitude
** Changed in: upstart
Status: Triaged = Fix Released
** Changed in: upstart (Ubuntu)
Status: Invalid = Fix Released
** Changed in: upstart
Assignee: (unassigned) = James Hunt (jamesodhunt)
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) = James Hunt (jamesodhunt)
Upstart in Natty now supports Override files and the manual stanza. See:
https://wiki.ubuntu.com/NattyNarwhal/TechnicalOverview#Upstart
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/94065
Title:
Another usercase. I want sometimes to enable Samba to share files with
someone, however, I don't want to have samba running all the time.
According to this
http://ubuntuforums.org/showthread.php?t=1468111page=2
Red Hat and Mandriva use service daemon off.
--
You received this bug notification
On Thu, Dec 30, 2010 at 8:53 AM, Scott James Remnant
94...@bugs.launchpad.net wrote:
Because, believe it or not, it's not a very common use case - in the
Debian and Ubuntu world, you're generally expected to uninstall
services you don't need.
Ah, but you want to use the service, you just don't
The feature planned for the next release is the support of override
files, which augment configuration files, so you'll be able to do:
echo manual /etc/init/apache.override
if you prefer
Scott
On Mon, Jan 3, 2011 at 6:24 PM, Bryan McLellan b...@loftninjas.org wrote:
On Thu, Dec 30, 2010 at
On Mon, Jan 3, 2011 at 10:58 AM, Scott James Remnant
94...@bugs.launchpad.net wrote:
The feature planned for the next release is the support of override
files, which augment configuration files, so you'll be able to do:
echo manual /etc/init/apache.override
I think that is a smart choice
That's the exact plan, yes
On Mon, Jan 3, 2011 at 9:08 PM, Bryan McLellan b...@loftninjas.org wrote:
On Mon, Jan 3, 2011 at 10:58 AM, Scott James Remnant
94...@bugs.launchpad.net wrote:
The feature planned for the next release is the support of override
files, which augment configuration
Sometimes users forget that some developers are assholes that don't care
about how they wish to use the software.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/94065
Title:
init: add
Do you often find that calling someone an asshole means they're more
likely do something you want? I must try that sometime ;-)
On Fri, Dec 31, 2010 at 4:36 AM, mikegrb mich...@thegrebs.com wrote:
Sometimes users forget that some developers are assholes that don't care
about how they wish to
Because, believe it or not, it's not a very common use case - in the
Debian and Ubuntu world, you're generally expected to uninstall
services you don't need.
Also the Dpkg package manager *honours* deletes as a conffile change,
so if you simply delete the job (or change its extension) it won't
expected to uninstall? says who? as the original submitter of this bug, let
me be the one to point out this phrase from the description: this might be to
temporarily disable a serial line getty, or whatever. that doesn't sound like
a reason to uninstall to me.
in any case, i think this
Indeed, all of those things work.
The reason for the .conf suffix is because editors frequently write
temporary working files into the same directory as the original file,
they also write backup files, and package managers frequently write
old or new files into the directory as well.
You end up
fair enough.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/94065
Title:
init: add non-destructive means to disable a job
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
The expected to uninstall comes from Debian Policy, btw. It
probably shouldn't be a surprise that Debian still to this day doesn't
provide a canon way to disable init scripts from running on boot aside
from uninstalling the package.
On Thu, Dec 30, 2010 at 5:49 PM, paul fox
it's not a very common use case
I wanted to desactivate avahi-daemon without uninstalling it.
I think ubuntu is generally use by desktop users.
A new user who want to optimize the computer ressource want to disable service
he don't use every day without taking the risk to uninstall it.
Today
Sometimes people forget that normal users don't care one iota about
what a service is, let alone which are running on their machine
On Fri, Dec 31, 2010 at 12:20 AM, plouf 94...@bugs.launchpad.net wrote:
it's not a very common use case
I wanted to desactivate avahi-daemon without uninstalling
No, my aim is to warn other users not to waste their time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/94065
Title:
init: add non-destructive means to disable a job
--
ubuntu-bugs mailing list
When does this spec https://launchpad.net/upstart/+spec/profiles will be
added to upstart ?
it is slightly embarassinng to not have a simple tool or a command line to
disable jobs at startup.
I'm really suprised such simple thing was not added from the beginning.
--
You received this bug
Note that in Upstart 0.6.7, you can disable a job with:
echo manual /etc/init/JOB.conf
(this bug isn't completely fixed yet, because we want to allow a
method to do that without modifying the original file)
On Wed, Dec 29, 2010 at 10:59 PM, plouf 94...@bugs.launchpad.net wrote:
When does
slightly embarassinng? Youre being very kind...
Its a complete shame for Upstart not to have ANY means to disable
services at startup.
More incredibly is that Ubuntu (and even Debian) is now migrating to it.
So now we are back to the old days of manually editing scripts? Hows
that ANY
Is there any recommended workaround?
--
init: add non-destructive means to disable a job
https://bugs.launchpad.net/bugs/94065
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Crazy as it may seem to replace the init system with one lacking this
most basic of functionality: no - there doesn't appear to be any
workaround.
--
init: add non-destructive means to disable a job
https://bugs.launchpad.net/bugs/94065
You received this bug notification because you are a member
If you comment out (#) the start on line, it effectively disables the
job while still making it available to start manually. This also ensures
that dpkg still sees it on upgrades and your changes aren't overwritten.
Not completely non-destructive, but it works.
--
init: add non-destructive means
Thanks, that will work for me.
@sPOiDar: This missing feature is not actually required for upstart to
do its job. It is, of course, very nice to have.
--
init: add non-destructive means to disable a job
https://bugs.launchpad.net/bugs/94065
You received this bug notification because you are a
On 14/09/10 02:40, Sergey Svishchev wrote:
@sPOiDar: This missing feature is not actually required for upstart to
do its job. It is, of course, very nice to have.
Upstart is an init system - being able to control which services are
started on boot on a host is core functionality,
Sounds like this functionality could be provided by implementing the
Profiles blueprint [1]?
[1] https://blueprints.launchpad.net/upstart/+spec/profiles
--
init: add non-destructive means to disable a job
https://bugs.launchpad.net/bugs/94065
You received this bug notification because you are a
For sanity's sake, I'm closing the Ubuntu tasks for upstream Upstart
bugs. I've experimented with having both, but it is just making bugs
hard to find now. Will use the policy whereby bugs on the Ubuntu
package exist in the Ubuntu packaging or patches only, any bugs in the
Upstart code are
where can i find the upstream bug?
--
init: add non-destructive means to disable a job
https://bugs.launchpad.net/bugs/94065
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
On Wed, 2010-04-07 at 16:27 +, paul fox wrote:
where can i find the upstream bug?
This is the upstream bug ;-)
Scott
--
Have you ever, ever felt like this?
Had strange things happen? Are you going round the twist?
--
init: add non-destructive means to disable a job
sorry. clearly i didn't parse the status change attached to comment #6
correctly. i thought it was this bug that had been marked invalid.
--
init: add non-destructive means to disable a job
https://bugs.launchpad.net/bugs/94065
You received this bug notification because you are a member of
Paul, Launchpad allows a single bug to be tracked in multiple places.
When the upstream bug tracker is supported by launchpad we can track
both the progress fixing the bug upstream, and the progress getting that
fix into Ubuntu as these don't happen simultaneously. Scott uses
launchpad to track
On Wed, 2010-04-07 at 17:47 +, Bryan McLellan wrote:
Scott, will this policy set the upstart bug to fixed when it is
committed to bzr or when it is fixed in an Ubuntu release? How will we
tell when the other happens?
Fix Released when a new upstream release of Upstart is made; which I
This feature is essential before we start moving certain services over
to upstart.
A example is to be able to start a server running mysql as a slave
without mysql starting automatically, as we would need to verify binary
log position between the servers first.
Installing memcached, but running
The plan in 0.10 is that jobs will be in automatic mode by default,
and can be placed into manual mode when necessary.
manual mode means that the job will still show up in lists, and new
instances will still be created as necessary, but they will not be
automatically started by Upstart.
A
48 matches
Mail list logo
