I'm running 10.04 and have had no issues. This bug specifically relates
to to the issue that was caused by a broken upstart config file.
Checking the source package right now, I see that the problem causing
this bug is still fixed. Can I suggest you open a different bug against
runit if you still c
Has anybody recently have problems with this? Since updating to 10.04, I
can't even start the daemon manually. I'm looking around for the scripts
but haven't found yet.
--
runsvdir does not start on boot
https://bugs.launchpad.net/bugs/439049
You received this bug notification because you are a m
OK, sorry for the misunderstanding. Everything runs fine now.
--
runsvdir does not start on boot
https://bugs.launchpad.net/bugs/439049
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
Ulf Klose,
the 2.0.0-1ubuntu3.1 package does precisely that. It defines a new
config file with the runlevels on one line.
--
runsvdir does not start on boot
https://bugs.launchpad.net/bugs/439049
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Paket: runit
Zustand: Installiert
Automatisch installiert: ja
Version: 2.0.0-1ubuntu3.1
Still doesn't start when having multiple lines for runlevels. Works fine
with the runlevels in one line as proposed in the first comment.
--
runsvdir does not start on boot
https://bugs.launchpad.net/bugs/439
This bug was fixed in the package runit - 2.0.0-1ubuntu3.1
---
runit (2.0.0-1ubuntu3.1) karmic-proposed; urgency=low
* Upstart doesn't appear to accept multiple "start on runlevel" lines. Replace
Upstart script with a version that uses a single line (closes LP: #439049).
-- Fra
I manually added this fix and that worked for me. No problems so far.
--
runsvdir does not start on boot
https://bugs.launchpad.net/bugs/439049
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
** Tags added: verification-done
** Tags removed: verification-needed
--
runsvdir does not start on boot
https://bugs.launchpad.net/bugs/439049
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
The version in karmic-proposed works fine for me.
--
runsvdir does not start on boot
https://bugs.launchpad.net/bugs/439049
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:/
** Branch linked: lp:ubuntu/karmic-proposed/runit
--
runsvdir does not start on boot
https://bugs.launchpad.net/bugs/439049
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:/
** Branch linked: lp:ubuntu/runit
--
runsvdir does not start on boot
https://bugs.launchpad.net/bugs/439049
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.co
Accepted into karmic-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Tags added: verification-needed
--
runsvdi
This bug was fixed in the package runit - 2.0.0-1ubuntu4
---
runit (2.0.0-1ubuntu4) lucid; urgency=low
[ Francis Russell ]
* Upstart doesn't appear to accept multiple "start on runlevel" lines. Replace
Upstart script with a version that uses a single line (closes LP: #439049).
Thanks, taking for sponsoring
** Changed in: runit (Ubuntu Karmic)
Status: Triaged => In Progress
** Changed in: runit (Ubuntu Karmic)
Assignee: (unassigned) => Chris Coulson (chrisccoulson)
--
runsvdir does not start on boot
https://bugs.launchpad.net/bugs/439049
You received this
Uploaded now
** Changed in: runit (Ubuntu Karmic)
Status: In Progress => Fix Committed
** Changed in: runit (Ubuntu Karmic)
Assignee: Chris Coulson (chrisccoulson) => (unassigned)
--
runsvdir does not start on boot
https://bugs.launchpad.net/bugs/439049
You received this bug notific
** Also affects: runit (Ubuntu Karmic)
Importance: Undecided
Status: New
** Changed in: runit (Ubuntu)
Importance: Undecided => Medium
** Changed in: runit (Ubuntu)
Status: New => Triaged
** Changed in: runit (Ubuntu Karmic)
Importance: Undecided => Medium
** Changed in:
Impact: runit is a collection of tools for process supervison. The bug
causes runsvdir not to start. This causes all services managed by runit
not to start defeating the entire purpose of the tool.
Patch Description: The bug appears to occur because of upstart not
accepting multiple "start on runl
** Tags added: packaging
--
runsvdir does not start on boot
https://bugs.launchpad.net/bugs/439049
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/mailman
Regardless, we seem to have a fix and Karmic's been released. Is there
someway we can get this fix pushed to the package?
--
runsvdir does not start on boot
https://bugs.launchpad.net/bugs/439049
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Without a full specification of the conf file, it's impossible to say
for certain. I couldn't find one, but I did find this:
http://upstart.ubuntu.com/wiki/ComplexEventConfig?highlight=((CategorySpec))
which suggests with the foo and bar example that multiple "start on"
lines should be supported.
I confirm that the fix works. This seems like an upstart bug though,
isn't it?
--
runsvdir does not start on boot
https://bugs.launchpad.net/bugs/439049
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
I can confirm this bug appearing on an i386 karmic install upgraded from
jaunty.
On my system, editing /etc/init/runsvdir.conf so that
start on runlevel 2
start on runlevel 3
start on runlevel 4
start on runlevel 5
was replaced by
start on runlevel [2345]
seems to have fixed it.
--
runsvdir
22 matches
Mail list logo
