Here's a far simpler patch - it just skips the respawn handling entirely
(including all the "failed" stuff) if the job is being stopped anyway.
I think this is probably "right"
** Patch added: "upstart-1.2-respawn-pre-stop.patch"
https://bugs.launchpad.net/upstart/+bug/568288/+attachment/3446
I haven't read the patent in question, general advise by my employers is
not to read them, but I can note a few particulars of ureadahead with
regards to the date you quote:
Development on ureadahead began in October 2009, it was based on Intel's
sreadahead for which development began in November
-c1326 doesn't change the console handling, it merely changed the error
case:
- if (system_setup_console (CONSOLE_OUTPUT, (! restart)) < 0)
+ if (system_setup_console (CONSOLE_OUTPUT, (! restart)) < 0) {
The Plymouth-safe console behavior was never committed upstream,
Please don't subscribe people to bugs without their permission
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/880049
Title:
100% CPU usage in init if /dev/console is not available
To manage notifica
The latter bit isn't true; current Chrome OS developer firmware will allow
you to boot any developer-signed USB stick.
But it is true that these have to be laid out so that the Chrome OS firmware
understands them, which means EFI, the particular GPT layout, etc. not as a
standard El Torito image o
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.
https://bugs.launchpad.net/bugs/94
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
** Package changed: ubuntu => upstart (Ubuntu)
** Changed in: upstart
Status: Triaged => In Progress
** Changed in: upstart
Assignee: (unassigned) => James Hunt (jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
I've marked the upstream task as Invalid since there is no chroot
support upstream, and this is otherwise covered by #430224init:
support chroots
** Changed in: upstart
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: upstart (Ubuntu)
Status: Invalid => New
** Changed in: upstart (Ubuntu)
Importance: Low => Undecided
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase-workspace in ubuntu.
https://bugs.launchpad.net/bugs/183729
** Changed in: upstart
Status: Fix Committed => Fix Released
** Also affects: upstart (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/522197
** Changed in: upstart
Status: Fix Committed => Fix Released
** Changed in: upstart (Ubuntu)
Status: Invalid => New
** Changed in: upstart (Ubuntu)
Importance: Low => Undecided
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: upstart
Status: Fix Committed => Fix Released
** Changed in: upstart (Ubuntu)
Status: Invalid => New
** Changed in: upstart (Ubuntu)
Importance: Low => Undecided
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: upstart
Status: Fix Committed => Fix Released
** Also affects: upstart (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/604227
** Changed in: upstart
Status: Fix Committed => Fix Released
** Also affects: upstart (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/619269
** Changed in: upstart
Status: Fix Committed => Fix Released
** Also affects: upstart (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/707151
http://bazaar.launchpad.net/~upstart-devel/upstart/trunk/revision/1272
** Changed in: upstart
Status: Triaged => Fix Committed
** Changed in: upstart
Milestone: None => 1.1
** Changed in: upstart
Assignee: (unassigned) => Scott James Remnant (scott)
--
You received
http://bazaar.launchpad.net/~upstart-devel/upstart/trunk/revision/1270
** Changed in: upstart
Status: Triaged => Fix Committed
** Changed in: upstart
Milestone: None => 1.1
** Changed in: upstart
Assignee: (unassigned) => Scott James Remnant (scott)
--
You received
** Changed in: upstart
Status: New => Confirmed
** Changed in: upstart
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/728531
Title:
chroot support is not relia
** Changed in: upstart
Status: Triaged => In Progress
** Changed in: upstart
Assignee: (unassigned) => James Hunt (jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
https://bugs.launchpad.net/bugs/430224
Title:
** Summary changed:
- mysql update fails waiting for upstart job to respawn
+ init: post-start can cause respawn to hang
** Changed in: upstart
Status: New => Triaged
** Changed in: upstart
Importance: Undecided => Medium
--
You received this bug notification because you are a member
Moved bug to Ubuntu bug tracker
** Project changed: upstart => null
** Changed in: null
Status: New => Invalid
** Also affects: ubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
*** This bug is a duplicate of bug 348455 ***
https://bugs.launchpad.net/bugs/348455
** This bug has been marked a duplicate of bug 348455
init: transfer state across re-exec
* You can subscribe to bug 348455 by following this link:
https://bugs.launchpad.net/upstart/+bug/348455/+subscrib
*** This bug is a duplicate of bug 348455 ***
https://bugs.launchpad.net/bugs/348455
** This bug is no longer a duplicate of bug 694772
Sudden reboot during server ISO install
** This bug has been marked a duplicate of bug 348455
init: transfer state across re-exec
* You can subscribe t
** Summary changed:
- restart command fails to restart main process when pre-stop stanza exists
+ init: restart command fails to restart main process when pre-stop stanza
exists
** Changed in: upstart
Status: Confirmed => Triaged
** Changed in: upstart
Importance: Undecided => Medium
Moved to Ubuntu bug tracker
** Changed in: upstart
Status: New => Invalid
** Also affects: upstart (Ubuntu)
Importance: Undecided
Status: New
** Project changed: upstart => null
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
It seems that this has been assigned to the upstream Upstart project
without a rationale for why this is not a bug in the Ubuntu
configuration. Unless you're sure there is an /sbin/init *code bug*, the
correct place for bug reports, even about boot, is in the appropriate
Ubuntu package.
This seems
** Summary changed:
- inconsistent terminology in man 5 init
+ doc: better define job, service & task
** Changed in: upstart
Status: New => Triaged
** Changed in: upstart
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: upstart
Status: New => Triaged
** Changed in: upstart
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/616575
Title:
init: support relation o
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 subscrib
*** This bug is a duplicate of bug 431239 ***
https://bugs.launchpad.net/bugs/431239
** This bug has been marked a duplicate of bug 431239
initctl: output better errors than D-Bus (e.g. for permission denied)
* You can subscribe to bug 431239 by following this link:
https://bugs.launchpad
The trouble with operators like "<", ">", etc. is that their meaning
varies depending on your interpretation of the following string.
It may be that dpkg-ish version comparisons are the right way forward
here, since they split strings and numbers according to a well-defined
spec that is actually a
I clearly didn't test this well enough ;-)
On Thu, Mar 3, 2011 at 8:22 AM, James Hunt <728...@bugs.launchpad.net> wrote:
> Public bug reported:
>
> Current natty chroot support does not seem to work reliably. Logging
> into a natty schroot as root and running "initctl list" shows:
>
> plymouth-ups
** Changed in: upstart (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: upstart (Ubuntu)
Status: Fix Released => Fix Committed
** Also affects: upstart
Importance: Undecided
Status: New
** Changed in: upstart
Status: New => Fix Released
** Changed in:
** Changed in: upstart
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase-workspace in ubuntu.
https://bugs.launchpad.net/bugs/183729
Title:
compat: utmp not cleared on tty logout
--
kubu
** Changed in: upstart
Status: Fix Committed => 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/720573
Title:
Segmentation fault on ".conf" file in /etc/init
--
ubuntu-bugs maili
Yeah there are quite a few bugs related to pre-stop scripts, they don't
really work like any other, so there are definite gaps in the coverage
On Thu, Feb 24, 2011 at 8:00 AM, scm <703...@bugs.launchpad.net> wrote:
> I can confirm I see this behavior in upstart (0.6.5-8) on lucid. On
> several of
No, restart means to restart what you already have.
If you restart a game, it means going back to the beginning of the game and
starting it again. It doesn't mean potentially starting a new completely
different game.
Scott
On Fri, Feb 18, 2011 at 7:10 AM, Thomas Schweikle <707...@bugs.launchpad
http://bazaar.launchpad.net/~upstart-devel/upstart/trunk/revision/1260
** Changed in: upstart
Status: In Progress => Fix Committed
** Changed in: upstart
Milestone: None => 1.0
** Changed in: upstart
Assignee: (unassigned) => Scott James Remnant (scott)
--
You rece
** Changed in: upstart
Milestone: None => 1.0
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase-workspace in ubuntu.
https://bugs.launchpad.net/bugs/183729
Title:
compat: utmp not cleared on tty logout
--
kubuntu-bugs mailing l
The best fix is in the filter, since it covers both.
As well as just checking that there is a ".conf" extension, make sure
that the previous character isn't "/"
** Changed in: upstart
Status: Triaged => In Progress
** Patch added: "conf-file-fix.patch"
https://bugs.launchpad.net/upsta
The reason it doesn't cause a panic on the reboot is because the file
doesn't actually get to the filesystem! If it did, you wouldn't be able
to boot again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
The attached patch adds test cases to check for this case, along with a
simpler similar test case for a file missing the ".conf" extension
(which is tested elsewhere, but always worth checking again).
This shows that the failure is an assertion:
test:job_class.c:153: Assertion failed in job_class
Confirmed; interestingly this doesn't seem to cause a kernel panic if
the file already exists on startup, just on first creation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/720573
Title:
Segmenta
This is definitely the intended behavior, the purpose of the pre-stop
script is to allow the job to:
- delay the stop
- cancel the stop
- send its own clean shutdown command before the TERM signal
It's also not inconsistent if you think about it. The starting event
happens before the pre-star
AM -0000, Scott James Remnant wrote:
>> They definitely should be allowed, ssh is actually a canon example of
>> why.
>
>> Upstart should supervise the sshd daemon, not the login sub-process
>> associated with a particular connection, and certainly not any
>> pro
They definitely should be allowed, ssh is actually a canon example of
why.
Upstart should supervise the sshd daemon, not the login sub-process
associated with a particular connection, and certainly not any
processes being run inside the login session.
Otherwise "stop ssh" would kill all user logi
I believe there's a bug open for the lack of state transfer? If not,
we could repurpose this one?
That being said, we should remember that state transfer should *not*
be invoked by SIGTERM - so maybe it's worth keeping this one open to
remind us of that.
Scott
On Fri, Feb 4, 2011 at 4:42 PM, Cl
This is this way by design, it allows for services to be restarted
without a change of configuration.
If you want to adopt the new configuration use:
stop service ; start service
** Changed in: upstart
Status: New => Won't Fix
--
You received this bug notification because you are a me
So one interesting thing about this is that if you design a system
that complains about its configuration during boot, then you're
complaining at the wrong person, the user. The user has no idea how
the system boots, and should have no need to know.
The system should boot regardless, and it _shou
At least certified bugs can be documented, with certified workarounds.
On Wed, Feb 2, 2011 at 2:05 PM, ingo <672...@bugs.launchpad.net> wrote:
>> ... freeze updates for 10.04.2 in order that we can get certification
> done
>
> That means we get certified BUGS - and that 10 months after release!
>
ingo: that's the way the Ubuntu release process works, I'm sorry that
this is a surprise to you
On Mon, Jan 24, 2011 at 1:00 PM, ingo <672...@bugs.launchpad.net> wrote:
> @Zippo,
>
> it is really a sad story with LTS-Lucid. I really don't understand how
> such a buggy release could pass QC (if the
Thanks for subscribing the Technical Board to this bug.
Please add discussion of the default NTP Servers to the agenda for the
next Technical Board meeting that you are able to attend, and we will
discuss it with you there.
Scott
On Sun, Jan 23, 2011 at 2:21 AM, Xavier Robin <104...@bugs.launchp
A D-Bus interface to re-exec is the plan here.
Scott
On Tue, Jan 4, 2011 at 2:37 PM, Loïc Minier wrote:
> Hey Scott!
>
> We'd love your input on the best way for upstart's telinit to not
> SIGTERM what could possibly be a non-upstart init (this is particularly
> an issue with busybox as it reboo
That's the exact plan, yes
On Mon, Jan 3, 2011 at 9:08 PM, Bryan McLellan 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 au
t off this email too long hoping I'd
> have more time to think about a solution than I have had.
>
> It must not require modifying the contents of a configuration file
> that other packages or the user owns.
> It should be simple, perhaps even simple enough that a user would
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 wrote:
> Sometimes users forget that some developers are assholes that don't care
> about how they wish to use the software.
>
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 uninsta
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
wrote:
> fair enoug
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
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
com
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 doe
I've no idea why that revision got dropped from the Ubuntu package, I
did a bit of investigation and it seems to vanish about the point we
switched to the auto-importer based packages. My only guess is that
bzr undid the cherry-pick as part of a merge.
Right, eglibc's postinst should definitely n
29 at 00:06 +0000, Scott James Remnant wrote:
>> Are you sure? I can't find that code at all - it looks like it's been
>> lost somehow
>
> quite certain.. its a bit tricky to find it in bzr, but this will give
> it to you for, say, maverick:
>
> $ bzr bran
Are you sure? I can't find that code at all - it looks like it's been
lost somehow
On Tue, Dec 28, 2010 at 6:19 PM, Clint Byrum wrote:
> On Tue, 2010-12-28 at 14:22 +, Scott James Remnant wrote:
>> On Tue, Dec 28, 2010 at 6:47 AM, Clint Byrum wrote:
>>
>&
On Tue, Dec 28, 2010 at 6:47 AM, Clint Byrum wrote:
> This makes sense, because telinit u just sends SIGTERM to upstart, which
> has no handler, as it was removed by revision 977, and doesn't seem to
> have been added back. Since SIG_DFL signals are not delivered to init,
> I'm not sure how umoun
On Mon, Dec 27, 2010 at 10:17 PM, Clint Byrum wrote:
> So this does in fact seem to be caused completely by init holding
> libraries open. I patched /etc/init.d/umountfs to save the output of
> lsof just before unmounting root:
>
Yes, now go read /etc/init.d/umountroot
** Changed in: upstart
I've just done a build of 0.6.7-1 on the natty userspace but maverick
kernel, and it built just fine
** Package changed: upstart (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
** Changed in: upstart
Status: Triaged => Fix Committed
** Changed in: upstart
Assignee: (unassigned) => Petr Lautrbach (plautrba)
** Changed in: upstart
Milestone: None => 0.6.8
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed
** Changed in: manpages (Ubuntu)
Assignee: Scott James Remnant (Canonical) (canonical-scott) => James Hunt
(jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/252413
Title:
Boot(7)
Ah, then ssh already had that race.
In which case -D seems like a good choice
On Mon, Dec 13, 2010 at 11:05 PM, Clint Byrum wrote:
> The code looks something like this:
>
> [ option parsing, config check, etc ]
> sshd.c, line 1744: daemon()
> [ reinit logs, start random number generator, chdir
Not using "expect fork" of course would mean that ssh would be reported as
running before it was actually listening for connections.
On Mon, Dec 13, 2010 at 10:13 PM, Clint Byrum wrote:
> In looking at the code in OpenSSH, the -D flag only affects this portion
> of sshd.c, around line 1740:
>
>
*** This bug is a duplicate of bug 26227 ***
https://bugs.launchpad.net/bugs/26227
** This bug is no longer a duplicate of bug 26227
udev: Update from 0.074-3 to 0.076-1 fails
** Changed in: udev (Ubuntu)
Assignee: Scott James Remnant (scott) => (unassigned)
** This bug has b
On 24/11/2010 16:03, David Paleino wrote:
>> That's why I never took the time out to do the update - it would have
>> been a hiatus in the boot performance work mucking around with the
>> charting tools, and what we have now worked well enough.
>>
>>
>> I'm not saying we shouldn't do the update, we
So it's worth clearing up a few misconceptions about our bootchart
packages and bootchart2.
The main two differences between bootchart and bootchart2 is that
bootchart2 replaces the original Java charting component with one based
on "pybootchartgui", a Python rewrite; and that it replaces the orig
** Changed in: upstart (Ubuntu)
Status: In Progress => Fix Released
--
upstart-job: refers to force-reload(8) instead of reload(8)
https://bugs.launchpad.net/bugs/532862
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
Oh, I think btrfs is busted, as also may be crypted disk
--
Misdetects my root partition as HDD on an SSD drive
https://bugs.launchpad.net/bugs/674435
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bu
** Changed in: mountall (Ubuntu)
Assignee: Scott James Remnant (scott) => (unassigned)
--
/tmp is not cleaned when on a separate partition
https://bugs.launchpad.net/bugs/478392
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
** Changed in: mountall (Ubuntu)
Assignee: Scott James Remnant (scott) => (unassigned)
--
mountall does not honor nobootwait flag on /var/* and /usr/* filesystems
https://bugs.launchpad.net/bugs/654545
You received this bug notification because you are a member of Ubuntu
Bugs, which
http://bit.ly/aro1lo
--
LVM - /var failed to mount during boot
https://bugs.launchpad.net/bugs/561390
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
https://lists.ubuntu.com/mail
One thing to bear in mind is that there's no point simply copying existing
pIQad glyphs, since coverage for those is provided by other fonts already -
and it's not clear that the pIQad glyphs are modifiable.
On Wed, Sep 29, 2010 at 12:56 AM, Launchpad Bug Tracker <
650...@bugs.launchpad.net> wrote
** Changed in: ureadahead (Ubuntu Maverick)
Assignee: Canonical Foundations Team (canonical-foundations) => Scott
James Remnant (scott)
--
ureadahead generating oom messages during boot.
https://bugs.launchpad.net/bugs/600359
You received this bug notification because you are a member
While I appreciate that it's always frustrating to be affected by a bug
that seems like it's going "un-addressed for years", I'm not aware of
any new information on this bug? Previous attempts at fixing it haven't
helped or have made things worse - and without a new line of
investigation, we're pr
Moved this back to kdm - while I appreciate there is a "Upstart could be
better" issue in here, there's more than enough of those filed upstream
and I'm hard at work on the next version of Upstart -- there's no quick
fix in Upstart for dealing with this kind of sequencing issue yet
The fix for thi
The solution you suggest is not a fix, since then it would mean that
/tmp is being cleaned up while other parallel processes are potentially
adding to it.
There isn't a known good fix for this yet
--
/etc/init/mounted-tmp.conf uses find, which is in /usr/bin
https://bugs.launchpad.net/bugs/52358
Robbie just pointed me as this bug, so I'm glad to see it's got a fix.
Just wanted to confirm that while some of our issues in Lucid *were*
plymouth/X interaction issues, we discovered that many of them were - as
debugged above - caused by the isig flag being reapplied to
/dev/console.
We had to
*** This bug is a duplicate of bug 327823 ***
https://bugs.launchpad.net/bugs/327823
** This bug has been marked a duplicate of bug 565890
init: support output of starting tasks to console
* You can subscribe to bug 565890 by following this link:
https://bugs.edge.launchpad.net/ubuntu/+so
** Changed in: upstart (Ubuntu)
Status: Incomplete => Won't Fix
--
apt-get remove upstart wants to remove entire system
https://bugs.launchpad.net/bugs/609794
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Moved upstream, since the bug is in the Upstart code
--
init: environ_valid() does not accept dot in key
https://bugs.launchpad.net/bugs/567068
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
Ah, I'd read the following from the shell guide:
Variables set by the user must have a name consisting solely of alphabet‐
ics, numerics, and underscores - the first of which must not be numeric.
But SUS says, elsewhere:
Environment variable names used by the utilities in the Shell and
*** This bug is a duplicate of bug 183729 ***
https://bugs.launchpad.net/bugs/183729
** This bug has been marked a duplicate of bug 183729
compat: utmp not cleared on tty logout
--
tty login sessions do not correctly get updated in /var/run/utmp
https://bugs.launchpad.net/bugs/571988
You
** Changed in: upstart (Ubuntu)
Status: New => Won't Fix
--
put back sysvinit as an option
https://bugs.launchpad.net/bugs/601980
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.ubunt
Transferring this to Ubuntu sudo
** Project changed: upstart => null
** Changed in: null
Status: New => Invalid
** Also affects: sudo (Ubuntu)
Importance: Undecided
Status: New
--
Upstart and Sudo - Email for root
https://bugs.launchpad.net/bugs/627472
You received this bug no
** Changed in: upstart
Status: New => Invalid
--
MySQL upstart stop job does not cleanly shutdown mysql
https://bugs.launchpad.net/bugs/620441
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
I'm transferring this bug over to Ubuntu cron.
** Project changed: upstart => null
** Changed in: null
Status: New => Invalid
** Also affects: cron (Ubuntu)
Importance: Undecided
Status: New
--
cron doesn't run due to have a bug in upstart
https://bugs.launchpad.net/bugs/62309
This bug sounds very like a problem that Andy Whitcroft and Colin Watson
have been tracking as part of their vgafb/efifb work - if I were you, I
would talk to them before taking any action
--
Dell Studio XPS 13 no video
https://bugs.launchpad.net/bugs/615549
You received this bug notification bec
Martin: there can never be any "all video devices are up" case because a
video card can be hotplugged later.
--
Dell Studio XPS 13 no video
https://bugs.launchpad.net/bugs/615549
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
This and bug #530779 are fundamental due to Upstart's use of ptrace()
for fork following - a rewrite of Upstart is in progress which uses
other newer kernel mechanisms to follow forks and would not be
vulnerable to this kind of issue. However there's no "quick fix" to it,
and no way to backport tha
On Tue, 2010-08-24 at 16:23 +, Clint Byrum wrote:
> Can we abort the stop from pre-stop somehow? Otherwise I'm afraid users
> will either be left waiting forever, or still sending SIGKILL.
>
You can call "start" from the pre-stop script, which will return the job
to a running state.
That bei
The OOM killer taking out ureadahead is not a problem; ureadahead will
have had at least some chance to do some good work.
ureadahead using excessive memory during tracing due to the size of the
tracing buffer is a different problem for which a fix has recently been
uploaded, and a further fix is
1 - 100 of 6900 matches
Mail list logo
