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
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
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
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.
** 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.
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
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 this bug
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 this bug
** 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
** 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/604227
** 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/522197
** 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
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
** 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
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:
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 almost
*** 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:
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
** 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
** 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
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
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
** 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
*** 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
*** 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:
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.
** 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
** 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:
** 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
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/720573
Title:
Segmentation fault on .conf file in /etc/init
--
ubuntu-bugs mailing
** 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
--
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
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:
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
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.
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
** 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
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 received this bug
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
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
, 2011 at 04:14:59AM -, 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
processes being run inside the login
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
, 2011 at 04:14:59AM -, 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
processes being run inside the login
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
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
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,
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!
--
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 there is
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 there is
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
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
A D-Bus interface to re-exec is the plan here.
Scott
On Tue, Jan 4, 2011 at 2:37 PM, Loïc Minier l...@dooz.org 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
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 want upstart to
start
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
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
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
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
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
, 2010-12-29 at 00:06 +, 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 branch lp:ubuntu/maverick/upstart maverick
$ cd
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
, 2010-12-29 at 00:06 +, 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 branch lp:ubuntu/maverick/upstart maverick
$ cd
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
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
On Tue, Dec 28, 2010 at 6:47 AM, Clint Byrum cl...@fewbar.com 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
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 cl...@fewbar.com wrote:
On Tue, 2010-12-28 at 14:22 +, Scott James Remnant wrote:
On Tue, Dec 28, 2010 at 6:47 AM, Clint Byrum cl...@fewbar.com wrote
On Tue, Dec 28, 2010 at 6:47 AM, Clint Byrum cl...@fewbar.com 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
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 cl...@fewbar.com wrote:
On Tue, 2010-12-28 at 14:22 +, Scott James Remnant wrote:
On Tue, Dec 28, 2010 at 6:47 AM, Clint Byrum cl...@fewbar.com wrote
On Mon, Dec 27, 2010 at 10:17 PM, Clint Byrum cl...@fewbar.com 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
On Mon, Dec 27, 2010 at 10:17 PM, Clint Byrum cl...@fewbar.com 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
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.
** 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
** 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 to
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 cl...@fewbar.com wrote:
The code looks something like this:
[ option parsing, config check, etc ]
sshd.c, line 1744: daemon()
[ reinit logs, start random number
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 cl...@fewbar.com wrote:
The code looks something like this:
[ option parsing, config check, etc ]
sshd.c, line 1744: daemon()
[ reinit logs, start random number
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 cl...@fewbar.com wrote:
In looking at the code in OpenSSH, the -D flag only affects this portion
of sshd.c, around
*** 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 been
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 cl...@fewbar.com wrote:
In looking at the code in OpenSSH, the -D flag only affects this portion
of sshd.c, around
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 certainly
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
** 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.
--
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
** 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
** 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 Ubuntu
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
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
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 this
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
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
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
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
1 - 100 of 6846 matches
Mail list logo
