I'm not sure why you've filed this on Upstart, since you seem sure it's
a Kernel issue and your description to me does sound like it's a kernel
driver bug hanging the machine if the resolution is wrong
Reassigning over to the kernel
** Package changed: upstart (Ubuntu) => linux (Ubuntu)
--
Kern
On Mon, 2010-04-12 at 13:52 +, Simon Oosthoek wrote:
> I'd like to see this bug re-opened, because there's still not sufficient
> documentation and some aspects of upstart indicate that it may be
> immature for a LTS release (IMHO).
>
If there are key areas of missing documentation that shoul
** Changed in: upstart
Status: New => Fix Released
--
doc: Upstart lacks documentation
https://bugs.launchpad.net/bugs/60429
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
** Changed in: initramfs-tools (Ubuntu)
Status: New => Fix Released
--
/var on separate partition fails at boot time
https://bugs.launchpad.net/bugs/555780
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
On Sat, 2010-04-10 at 22:02 +, Mathias Gug wrote:
> Scott, do you think this bug can be fixed in time for Lucid release?
>
Since we're well past all relevant freezes, and this is not exactly a
show-stopping bug, I don't see how.
Scott
--
Have you ever, ever felt like this?
Had strange thing
On Sun, 2010-04-11 at 01:37 +, Robert Collins wrote:
> Could we at least put it in the man page? (which will mean creating
> one ;))
>
Sure ;-) please contribute one!
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
no text version of plymouth-log-viewer
https://bugs.launchpad
command would do the trick.
>
Why should that be necessary?
If every single package needs to add that, that seems like a bug in
gettext? Should the po file not be automatically updated when the
package is built with "make && make install" ?
Scott
--
Scott James Remnant
sc..
Yes there is:
cat /var/log/boot.log
the only reason there's a special graphical version is to turn the
terminal escape sequences from colourification, etc. into something
renderable in graphical mode ;-)
Since you're dumping it to a terminal in text mode, cat on the log file
works just fine
*
We don't allow non-root users to access raw firewire devices since this
opens root access to the system through known flaws in the firewire
stack.
** Changed in: udev (Ubuntu)
Status: New => Won't Fix
--
Firewire is not allowed for normal users, it doesnt gives an udev rule for that.
http
There are no "log-priority" or "--debug" options for "start", I believe
you have confused the man page.
There are separate commands to initctl, for example:
initctl log-priority debug
initctl start
The first changes Upstart's logging priority, and the second starts the
service; you'll see m
This also appears in the source package:
wing-commander mountall% tar tf ../mountall_2.11.tar.gz| grep pot
mountall-2.11/po/mountall.pot
--
Mountall needs to generate pot file on build
https://bugs.launchpad.net/bugs/559997
You received this bug notification because you are a member of Ubuntu
Bu
Like every modern source package, mountall uses autoconf, automake and
dh(7) - and certainly generates a .pot file when made!
wing-commander mountall% ls -l po/mountall.pot
-rw-r--r-- 1 scott scott 1.9K 2009-12-11 11:12 po/mountall.pot
So I've no idea why this isn't picked up
** Changed in: moun
This isn't true at all.
The reason that there's no documentation that you need to do anything
special for mountall to support /var on a separate partition is because
you don't! You've pasted the appropriate lines from /lib/init/fstab for
/var/run and /var/lock and as you can see, they both have t
On Fri, 2010-04-09 at 13:39 +, Bernd Zeimetz wrote:
> > Upstart runs all shell scripts with "set -e" by default.
>
> So what if the script is *not* run by upstart, but by somebody trying to
> figure out why things work (or not)?
> If you need to assume that a piece of shell code is executed
Sounds quite plausible
Though this will also combine with the bug where "killprocs" kills all
Upstart jobs, so plymouth gets SIGTERM during the runlevel switch - and
that seems to result in plymouth exiting without restoring the console
--
switching from runlevel 5 to runlevel 1 locks up system
On Fri, 2010-04-09 at 10:30 +, Chris Jones wrote:
> I ran into this on a user's lucid laptop this morning, so re-opening
>
Could you run mountall --debug and capture the output (it should end up
in /var/log/boot.log now)
status incomplete
Scott
--
Scott James Remnant
sc...
Your system is continuously in I/O wait, I actually strongly suspect you
have a hardware problem here. Could you check all of the cables in the
computer are seated correctly, perhaps clean out dust, etc. as a
sensible debugging check
On the off-chance it's a driver problem, I've reassigned the ta
*** This bug is a duplicate of bug 551879 ***
https://bugs.launchpad.net/bugs/551879
** This bug has been marked a duplicate of bug 551879
Boot speed 20+ minutes when ureadahead enabled
--
boot hangs 20+ minutes
https://bugs.launchpad.net/bugs/556259
You received this bug notification bec
On Thu, 2010-04-08 at 23:17 +, dedded wrote:
> Is there any possibility that this script, as patched, still fails
> catastrophically if MOUNTPOINT is defined to a non-existent directory,
> or if /tmp doesn't exist?
>
The "cd ${MOUNTPOINT}" will fail, and the script will exit; that's why
it's
eprofile ureadahead
> and attach the 3 logs from that. here is a link to the output of "mount":
> http://docs.google.com/Doc?docid=0AeqU_ryw50fpZDNiYmJtNl8yY3dzejRoZHo&hl=en
> and i'll be back in about 20 minutes...
>
That's very very very very very very odd.
S
We put a lot of effort to keep our display managers on VT7, and don't
have a flicker with Plymouth (which also uses VT7)
** Changed in: gdm (Ubuntu)
Status: New => Won't Fix
** Changed in: kdebase-workspace (Ubuntu)
Status: New => Won't Fix
** Changed in: consolekit (Ubuntu)
** Package changed: base-files (Ubuntu) => dpkg (Ubuntu)
--
package base-files 5.0.0ubuntu14 failed to install/upgrade: error writing to
'': Input/output error
https://bugs.launchpad.net/bugs/557630
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Sounds like a kdm issue, then
** Package changed: ubuntu => kdebase-workspace (Ubuntu)
--
VT switch not work with GT240
https://bugs.launchpad.net/bugs/554818
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase-workspace in ubuntu.
--
kub
from the system
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
[G72M] Screen corruption when using KMS. Dell Latitude D620 / Quadro NVS
110M/GeForce Go 7300
https://bugs.launchpad.net/bugs/539730
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
It sounds like you experienced the problem where mountall would block
waiting for Plymouth, without noticing that (a) plymouth wasn't running
or (b) what it was waiting for actually showed up
This was fixed in 2.10, and you say you've not experienced the bug for a
while which fits
If you have a r
Marking as Invalid since the original reporter no longer has the
hardware.
--
after deleting pack file, first boot is fast, subsequent boots are slow
https://bugs.launchpad.net/bugs/491956
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Perran: your ureadahead dump is very truncated - could you try this:
sudo ureadahead --dump > dump.txt
that should give a full dump - if you could file a new bug using
"ubuntu-bug ureadahead" I'd appreciate that - since that will give me
the key details of your system
Thanks
** Changed in: ur
dguennewig, I can confirm that your problem is covered by bug #518204 -
we shouldn't include large files like LUKS
--
after deleting pack file, first boot is fast, subsequent boots are slow
https://bugs.launchpad.net/bugs/491956
You received this bug notification because you are a member of Ubunt
Note that your ureadahead dump looks normal, no alarming issues here:
/var/lib/ureadahead/pack: created Tue, 30 Mar 2010 06:58:30 + for hdd 8:1
13 inode groups, 953 files, 1044 blocks (88432 kB)
Could you also attach the output of running "mount" for me? Thanks!
--
Boot speed 20+ minutes
Hi there, thanks for the report and your patience!
Unfortunately the image links you've supplied don't work - they just
direct me to the "imageshack.us" front page. Could you attach the
original files directly to this bug (it allows you to upload)
** Changed in: ureadahead (Ubuntu)
Status
*** This bug is a duplicate of bug 491943 ***
https://bugs.launchpad.net/bugs/491943
Hey there, thanks for taking the time to make this report.
Since your problem is during reprofiling, and looking up the spec of
your machine, it looks like this is caused by the extremely large memory
overhea
** Summary changed:
- ubuntu-bug ureadahead 20+ minute boot
+ Boot speed 20+ minutes when ureadahead enabled
--
Boot speed 20+ minutes when ureadahead enabled
https://bugs.launchpad.net/bugs/551879
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm sorry to hear that you're having problems. ureadahead is certainly
supposed to speed up your boot, especially on HDD which is what it's
optimised for (not SSD)
Could you do the following for me, this will allow me to get an idea of
where the problem might be and suggest further tests:
1. in
Thanks for the report.
After doing this, could you run "sudo ureadahead --dump" and attach the
output -- also could you attach the contents of
/sys/kernel/debug/tracing/trace
I have a hunch that the missing files are relative paths, which requires
an improved kernel patch (I actually have a propo
** Package changed: ureadahead (Ubuntu) => gdm (Ubuntu)
--
can't login in gnome
https://bugs.launchpad.net/bugs/546680
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://list
*** This bug is a duplicate of bug 522197 ***
https://bugs.launchpad.net/bugs/522197
This message is harmless.
Marking as a duplicate of the bug that the message is shown at all
** This bug has been marked a duplicate of bug 522197
init: shouldn't log a warning/error when a job fails with
Hi there, thanks for the report.
status 5 usually means that you have /var mounted on a separate
partition, is that true?
The mountall errors are a knock-on effect of an earlier bug that should
already be fixed, did exiting from this shell fix the issue for you?
** Changed in: ureadahead (Ubuntu
The sreadahead package left on your system is not actually sreadahead,
but a package intended to clean up sreadahead's data files on upgrade -
it's intended to be safely removed.
Leaving this bug open to remind us that the package can be dropped in
Maverick
** Summary changed:
- do-relase-upgrad
*** This bug is a duplicate of bug 523484 ***
https://bugs.launchpad.net/bugs/523484
** This bug has been marked a duplicate of bug 523484
ureadahead requires /var on root filesystem
--
relies on having /var on the same fs as root?
https://bugs.launchpad.net/bugs/53
You received this
*** This bug is a duplicate of bug 497299 ***
https://bugs.launchpad.net/bugs/497299
** This bug has been marked a duplicate of bug 497299
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
--
Problem with system services during boot
https://bugs.launchpad.net/bugs/5
Hey there, thanks for filing this report.
This is actually quite normal, when removing a package with "remove"
configuration files and other miscellaneous data are left so that should
you chose to reinstall, any changes you've made are preserved.
To remove these, you need to "purge" the package,
The FHS only really allows us /var to store things like this, sadly
** Summary changed:
- ureadahead.conf assumes that /var/lib/ureadahead is available on startup
+ ureadahead requires /var on root filesystem
** Changed in: ureadahead (Ubuntu)
Importance: Undecided => Medium
** Changed in: u
Hi there, and thanks for the taking the time to write the mail. From
what I can tell, there's no actual bug you are reporting here, but
merely asking about the mechanism by which Upstart can determine that a
daemon is "ready". I'll mark this report out as "Invalid" for lack of a
better status to
This should be moved over to the kernel - since the rotational flag is
wrong for this drive.
As to why the pre-start script you tried to override it didn't work,
could you post the output of "mount" for me so I can test your sed
script? I have a feeling you may be accidentally trying to toggle th
Very large files is probably the right cut-off
** Summary changed:
- ureadahead should exclude kvm image files
+ Should exclude very large files
--
Should exclude very large files
https://bugs.launchpad.net/bugs/518204
You received this bug notification because you are a member of Ubuntu
Bugs,
** Visibility changed to: Public
** Summary changed:
- ureadahead crashed with SIGSEGV in main()
+ ureadahead crashed with SIGSEGV in trace_add_path()
** Changed in: ureadahead (Ubuntu)
Status: New => Confirmed
--
ureadahead crashed with SIGSEGV in trace_add_path()
https://bugs.launchpa
Marking the sreadahead task as Invalid since that package isn't in
Ubuntu anymore - this is still an open bug on ureadahead.
The tracing overhead for an online retracing is basically zero. Offline
retracing like we do know can slow down the boot by over three or four times!
** Changed in: srea
I think what's happening here is that ureadahead mounts
/var/lib/ureadahead/debugfs so that it can work before the actual
/sys/kernel/debug path is mounted. mountall is running, and sees that
debugfs gets mounted at the new path, and records it to be added to
/etc/mtab when the root filesystem is
Will use bug #501715 for that
--
Kernel trace buffer should be set to less unrealistic value
https://bugs.launchpad.net/bugs/491943
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
Another point is that the trace buffer is not shrunk after profiling;
this was for my own debugging, but I think by default we should reclaim
this kernel memory
--
Kernel trace buffer should be set to less unrealistic value
https://bugs.launchpad.net/bugs/491943
You received this bug notification
** Summary changed:
- ureadahead doesn't reduce tracing buffer after profile
+ Kernel trace buffer should be cleared and size restored after profiling
** Changed in: ureadahead (Ubuntu)
Importance: Medium => High
--
Kernel trace buffer should be cleared and size restored after profiling
http
Tormod: the problem there is that the "needed pieces" are rarely only at
the start of the disk - it's probably better to spend the effort on a
defragmenter so that they are!
rafal: ureadahead tries to utilise the disk as much as it can - the fact
it can't reach 100% is because the time is lost see
Added a kernel bug task - Kernel folks, this is the "bug" for that "load
into the page cache without opening" patch we keep talking about
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
open()ing files takes a long time with low throughput
https://bugs.launchpad.ne
** Summary changed:
- man page needs to be updated
+ Manual page still refers to "removed if a month old"
--
Manual page still refers to "removed if a month old"
https://bugs.launchpad.net/bugs/482767
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
This is set to 128MB or something at the moment; that's ridiculously
high
--
Kernel trace buffer should be set to less unrealistic value
https://bugs.launchpad.net/bugs/491943
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
This is set to 128MB or something at the moment; that's ridiculously
high
** Summary changed:
- When trying to profile on a system with 512MB -- get a kernel OOM
+ Kernel trace buffer should be set to less unrealistic value
** Changed in: ureadahead (Ubuntu)
Status: Confirmed => Triaged
On Tue, 2010-04-06 at 19:11 +, RussianNeuroMancer wrote:
> No. Screen on text-consoles cleared after kdm shown login screen in
> X-session.
>
Could you elaborate what you mean here?
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
VT switch not work with GT240
https://bugs.laun
ying it is s...
>
I am not aggressive. I am merely terse.
The workaround is wrong because the "local-filesystems" event depends on
udev running.
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
upstart fails to boot with NVidia proprietary driver and several partitions
https:
ntu)
Importance: Undecided => High
** Changed in: mountall (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: mountall (Ubuntu)
Assignee: (unassigned) => Scott James Remnant (scott)
** Changed in: mountall (Ubuntu)
Milestone: None => ubuntu-10.04
--
init: su
Wow.
You guys need to chill out ;-)
I'm sorry that you got confused that moving the bug from "upstart
(Ubuntu)" to just "upstart" involved marking it as _Invalid_ and opening
a new task; I think that's one of Launchpad's more idiotic design flaws
too.
I'm also sorry that I receive literally hund
made; which I
package and upload to Ubuntu as I make it ;-)
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
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 subscrib
On Wed, 2010-04-07 at 18:47 +, Lars Düsing wrote:
> Has anybody forwarded this problem to upstream?
>
Ubuntu are upstream for Upstart (I wrote it!)
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
init: job stuck with expect fork/daemon when parent reaps child
https://bugs.launchp
bug mountall", I would
really appreciate that.
It's quite possible that you each have a different problem at this
point.
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
Waiting for /some/partition [SM]
https://bugs.launchpad.net/bugs/527666
You received this bug notification because
Thanks, please do!
** Changed in: upstart (Ubuntu)
Status: Incomplete => Invalid
--
Upstart not starting jobs on boot
https://bugs.launchpad.net/bugs/543506
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Moved to Ubuntu bug tracker
** Also affects: ureadahead (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ureadahead (Ubuntu)
Status: New => Confirmed
** Changed in: ureadahead (Ubuntu)
Importance: Undecided => High
** Changed in: ureadahead
Status: Confirmed
Moved to Ubuntu bug tracker
** Also affects: ureadahead (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ureadahead (Ubuntu)
Status: New => Incomplete
** Changed in: ureadahead
Status: Incomplete => Invalid
** Changed in: ureadahead (Ubuntu)
Importance: Undec
Moved to Ubuntu bug tracker
** Also affects: ureadahead (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ureadahead (Ubuntu)
Status: New => Invalid
** Changed in: ureadahead (Ubuntu)
Status: Invalid => New
** Changed in: ureadahead
Status: New => Invalid
Moved to Ubuntu bug tracker
** Also affects: ureadahead (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ureadahead (Ubuntu)
Status: New => Invalid
** Changed in: ureadahead (Ubuntu)
Status: Invalid => New
** Changed in: ureadahead
Status: New => Invalid
Moved to Ubuntu bug tracker
** Also affects: ureadahead (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ureadahead (Ubuntu)
Status: New => Invalid
** Changed in: ureadahead (Ubuntu)
Status: Invalid => New
** Changed in: ureadahead
Status: New => Invalid
Moved to Ubuntu bug tracker
** Also affects: ureadahead (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ureadahead (Ubuntu)
Status: New => Invalid
** Changed in: ureadahead
Status: New => Invalid
** Changed in: ureadahead (Ubuntu)
Status: Invalid => New
Moved to Ubuntu bug tracker
** Also affects: ureadahead (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ureadahead (Ubuntu)
Status: New => Triaged
** Changed in: ureadahead (Ubuntu)
Importance: Undecided => High
** Changed in: ureadahead
Status: Triaged => I
Moved to Ubuntu bug tracker
** Changed in: ureadahead
Status: Incomplete => Invalid
--
after deleting pack file, first boot is fast, subsequent boots are slow
https://bugs.launchpad.net/bugs/491956
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
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
https://bugs.launc
Actually, the mode change is caused by the framebuffer driver loading on
boot - this isn't changeable.
In the next version we're looking at moving this up so that the
bootloader sets the mode, and the kernel inherits that for its
framebuffer - this will prevent the screen clearing
** Package chan
The funny thing is that I have this one written down in my notes, but
never filed a bug for it. Thanks
** Summary changed:
- 'expect fork'+'respawn'+script+ENOENT => start/running w/o PID
+ init: failed exec() and "expect" cause hang or missing pid
** Changed in: upstart (Ubuntu)
Status:
Agreed, it should be made available in those processes that run
alongside. It probably makes sense to include it in the event as well,
so you could do:
on started apache
script
.. $APACHE_PID ...
end script
** Summary changed:
- Upstart should include pid as an environment variable
+
** Description changed:
Nouveau blacklisting fails when /usr is on seperate partition.
cat /etc/modprobe.d/nvidia-graphics-drivers.conf
blacklist nouveau
blacklist lbm-nouveau
blacklist nvidia-173
blacklist nvidia-96
alias nvidia nvidia-current
File exists as above and 'updat
The suggested change to udev.conf in that bug report is completely
wrong, incorrect, broken and busted - it will almost always result in
your system not booting
** Changed in: upstart (Ubuntu)
Status: New => Invalid
--
upstart fails to boot with NVidia proprietary driver and several parti
Thanks for the report.
At your debug shell, could you run the "initctl list" command for me,
and provide the output.
Also when booting, add --verbose to the kernel command line, and capture
the output from that.
Thanks very much
** Changed in: upstart (Ubuntu)
Status: New => Incomplete
This is definitely not an Upstart problem, however there is insufficient
information in this report to determine what the problem is. Please
read http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
** Package changed: upstart (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incom
I think the problem here is simply that killprocs (on entering runlevel
1) kills all Upstart-managed jobs, including Plymouth - so plymouth is
not cleanly shutdown, restoring the console
If you press Alt+F1, or Alt+F7, do you find the sulogin shell?
** Summary changed:
- [Lucid Beta] telinit doe
Unfortunately there just isn't enough information here to begin to
diagnose your problem. Please read
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
In particular, please give full details about what you changed, and what
you see on screen.
Either way, this is unlikely to be an Upstart is
The flashing caps lock light means you have experienced a kernel panic
** Summary changed:
- Upstart update causes boot to hang - Karmic/ Lucid
+ Kernel panic on boot
** Package changed: upstart (Ubuntu) => linux (Ubuntu)
--
Kernel panic on boot
https://bugs.launchpad.net/bugs/542407
You recei
*** This bug is a duplicate of bug 497299 ***
https://bugs.launchpad.net/bugs/497299
** This bug has been marked a duplicate of bug 497299
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
--
In Ubuntu Karmic 9.10 the upstart package version 0.6.3-11, don't initiate
Please also attach your /var/log/udev
--
Booting with the '--verbose' parameter results in a black screen
https://bugs.launchpad.net/bugs/542992
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
The --verbose parameter doesn't change anything other than potentially
making the boot slightly slower - this sounds more like a nouveau issue
** Package changed: upstart (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
Booting with the '--verbose' pa
** Summary changed:
- init.d script points to a program named force-reload, which does not exist
+ upstart-job: refers to force-reload(8) instead of reload(8)
--
upstart-job: refers to force-reload(8) instead of reload(8)
https://bugs.launchpad.net/bugs/532862
You received this bug notification
Moved this to be an Upstream bug.
I think that the most probably implementation will be that you declare
chroots in /etc/init.conf that you wish the init daemon to manage. init
will then also look in CHROOT/etc/init for jobs, and record these as
belonging to that chroot. All actions on these job
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 Upstre
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 Upstre
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 Upstre
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 Upstre
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 Upstre
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 Upstre
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 Upstre
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 Upstre
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 Upstre
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 Upstre
t/rc.conf technically
requires RUNLEVEL be set.
If we handle this at the Upstart-level, it makes more sense. So
something like:
# start mounted-tmp
start: Missing argument: MOUNTPOINT
Then you're more likely to do:
# start mounted-tmp MOUNTPOINT=/tmp
Scott
--
Scott James Remn
On Wed, 2010-04-07 at 14:21 +, Torsten Jerzembeck wrote:
> In my opinion, it is very definitely a wrong behaviour of any init
> script
>
This is not an init script.
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
mounted-tmp.conf erased complete server
https://bugs.launchpad
501 - 600 of 6900 matches
Mail list logo
