the twist?
=== modified file 'ChangeLog'
--- ChangeLog 2007-02-13 15:53:39 +
+++ ChangeLog 2007-02-16 10:20:21 +
@@ -1,3 +1,9 @@
+2007-02-16 Scott James Remnant [EMAIL PROTECTED]
+
+ * init/main.c (pwd_handler): Handle the SIGPWR signal by generating
+ the new event.
+ * init/event.h
On Sat, 2007-03-10 at 11:06 -0300, Hervé Fache wrote:
1. if the devices are on the same physical device (sda1, sda2,
sda5, ...), then you do NOT want them to run at the same time
Indeed; a future specification for Upstart should detail how we intend
to solve this. Any ideas?
Scott
--
Have
On Sat, 2007-03-10 at 19:35 +0100, paul wrote:
This is an elegant solution. What I was thinking of the following ( I
deal with root separately):
emit fs-checked $partition
This will block until the filesystem has been checked, as well as output
any status information.
On Sat, 2007-03-10 at 22:58 +0100, Matthias Urlichs wrote:
Scott James Remnant:
I'm still not sure what you mean, sorry? Could you explain a little
more?
As an example, say you have a system service that's used to sync PDAs or
whatever. That process needs to keep running as long
it.
Andrew Mitchell was working on patches for upstart, but they never saw
the light of day.
I'd like to see SELinux supported by it, as long as it's done properly
and not just hacked in any old way.
For example, could the policy be loaded in the initramfs rather than by
init?
Scott
--
Scott James
On Sun, 2007-03-18 at 09:49 -0400, Chad Sellers wrote:
On Mar 18, 2007, at 12:44 AM, Scott James Remnant wrote:
Actually the code to load the policy in sysvinit was coded directly
into
the init daemon (badly), so upstart simply doesn't support it.
Yes, this had to be put directly
On Sun, 2007-03-25 at 13:54 -0400, Brian J. Murrell wrote:
On Sun, 2007-25-03 at 18:37 +0100, Scott James Remnant wrote:
Upstart relies on being process #1 for various features to work, and
expects to be granted the special handling that the kernel gives to that
process.
Ahhh
On Mon, 2007-03-26 at 16:28 -0400, Brian J. Murrell wrote:
I was attempting to write an upstart script for mythtv-frontend and came
to the point where it wants to run as a different user. Is there any
way to do this with an upstart directive and then exec rather than
writing a script that
On Thu, 2007-04-19 at 10:02 +0300, Johan Kiviniemi wrote:
Scott must have been quite busy with the approaching release of Ubuntu
feisty. Since it was clear the planned new Upstart functionality wasn’t
going to arrive in time for feisty anyway, i assume more urgent things
have been prioritized
I've updated my main bzr branches of upstart and libnih to the 0.15/0.16
dirstate-tags format.
If you wish to do the same, make sure you have this version installed,
and run bzr upgrade --dirstate-tags on your branch.
The obvious benefit:
quest upstart% bzr tags
0.1.0[EMAIL
On Thu, 2007-07-12 at 02:34 +0200, Mildred wrote:
Sometimes, I want to restart a service and i must in order stop the
service then start it. Would it be possible to add the restart command
to initctl that would do that for me ?
Restart would be identical to stop then start on the same
On Thu, 2007-07-12 at 13:18 +0200, Philippe De Swert wrote:
I wondered if there was a way to get upstart to start daemons with another
user than root. This because some daemons don't drop there privileges
decently
(or as in my case I need the init system to start them up, but I need
While I traditionally dislike roadmaps, mostly due to their inevitable
inaccuracy, I think that it's useful at this point, especially given the
recent period of inactivity, to define one for the next major Upstart
milestone: 0.5.
The main goal of this milestone is to define the structure and
On Tue, 2007-10-16 at 22:35 +0200, Michael Biebl wrote:
2007/10/11, Scott James Remnant [EMAIL PROTECTED]:
Upstart, the IPC Server
---
One minor, trivial change that it almost doesn't seem worth mentioning.
Upstart's own home-brew IPC will be dropped, and instead
On Fri, 2007-10-19 at 12:33 +0200, Mildred wrote:
Personally I replaced init completely with upstart some months ago. And
I gained nothing in boot speed. Is was almost the same, or slower. I
can't say.
Depending on what set of scripts you had before, and which you
converted, this doesn't
On Mon, 2007-10-22 at 13:40 -0700, Shawn Rutledge wrote:
Another idea I had over the weekend to speed up boot times is also
related to reducing disk seek time. I see that ubuntu already starts
a readahead process before much else, to preload the necessary files
into RAM. This is an
On Tue, 2007-10-23 at 19:01 +0200, Mildred wrote:
Le Mon 22/10/2007 à 14:20 Shawn Rutledge à écrit:
It would probably be enough to have a different selection in the boot
loader, like the one for profile, which does not use the tarball at
all (and regenerates the tarball later).
Or it
On Tue, 2007-10-23 at 22:11 +0200, Jan Claeys wrote:
The parser is a string one; so it could be faster by being binary ...
but it wouldn't actually buy you anything; you'd have to re-parse the
text files on boot to make sure they hadn't been changed while the
computer was off.
Storing
On Sun, 2007-11-25 at 18:24 -0200, Ismael Luceno wrote:
Look at the following document:
http://ismael.linuxdevel.net/init_issues.html
A reasonably quick reply to the issues here in the interest of starting
debate. There's almost no text backing up why you think these things
are important, so
On Thu, 2007-11-29 at 21:32 +0100, Mildred wrote:
Le Mon 26/11/2007 à 23:43 Scott James Remnant à écrit:
Upstart, in the extraordinarily unlikely circumstance that it might
crash (0.3.8 hasn't had a single report of one in the 1 year+ it's
been out), simply forks and dumps core
I have renamed the development branches from main to trunk to better
match the practice of how we talk about them.
If you have existing branches you will need to update the saved location
for them:
bzr pull --remember http://bazaar.launchpad.net/~keybuk/libnih/trunk/
bzr pull --remember
This is an interim update to the Upstart 0.5 Roadmap sent to this
mailing list three months ago, which you can find the archives here:
https://lists.ubuntu.com/archives/upstart-devel/2007-October/000468.html
Stats
-
First, some stats on the development: the last released version of
Upstart
On Wed, 2008-01-16 at 12:45 +0100, Michael Biebl wrote:
2008/1/16, Scott James Remnant [EMAIL PROTECTED]:
[NEW] Service readiness announcement through SIGSTOP.
When services remain in the foreground, there's no usual
way for them to signal that they have completed
On Thu, 2008-01-17 at 12:37 +0100, Michael Biebl wrote:
2008/1/16, Scott James Remnant [EMAIL PROTECTED]:
On Wed, 2008-01-16 at 12:45 +0100, Michael Biebl wrote:
2008/1/16, Scott James Remnant [EMAIL PROTECTED]:
Disable a job from its definition, instead of just deleting
On Thu, 2008-01-17 at 23:24 +0100, Michael Biebl wrote:
2008/1/17, Scott James Remnant [EMAIL PROTECTED]:
On Thu, 2008-01-17 at 12:37 +0100, Michael Biebl wrote:
2008/1/16, Scott James Remnant [EMAIL PROTECTED]:
On Wed, 2008-01-16 at 12:45 +0100, Michael Biebl wrote:
2008/1/16
On Fri, 2008-01-25 at 14:24 -0800, eehouse.org wrote:
Let's say I have a job that gets stopped in a couple of ways:
stop on stopped foo
stop on stopped bar
You don't receive information about which events stopped you, since the
post-stop script should only clean-up the effects of the
On Thu, 2008-02-07 at 13:02 -0800, [EMAIL PROTECTED] wrote:
I want to modify /etc/event.d/ttyS2 to not launch getty when
/dev/ttyS2 is not present.
You could do it as a single script:
start on runlevel 2
stop on runlevel [!2]
pre-start exec [ -e /dev/ttyS2 ] || stop
On Wed, 2008-03-26 at 22:08 -0400, Bill Nottingham wrote:
In attempting to work through some upstart conversions, I've run into the
problem that there seems to be no way to require *multiple* events on start ,
i.e., 'start on X and Y'
This seems to be impossible in 0.3 (without resorting to
On Wed, 2008-04-23 at 13:21 +0200, Enrico Scholz wrote:
is there a way to re-read the configuration on filesystems without
inotify support? E.g. I develop on an embedded system which boots
from an NFS rootfilesystem (and has /etc/event.d on it). Rebooting
whole machine seems to be the only
On Thu, 2008-05-01 at 14:37 +0200, Epy wrote:
I'd like to point some french translations errors in help of the
'shutdown' command
Assuming that you're using Ubuntu, translations come from the
Rosetta/Launchpad Translations system and can be modified directly
there.
I don't have anything in
In the latest kernel releases, we got two exciting new facilities:
signalfd() and the timerfd_*() series. These allow us mortal
application developers to deal with signals and timers in our main loop
using just read().
To my mind, there's an obvious third one missing for which the name
waitfd()
On Wed, 2008-06-04 at 16:50 -0400, Jeremy Katz wrote:
On Wed, 2008-06-04 at 17:18 +0100, Scott James Remnant wrote:
On Wed, 2008-06-04 at 11:23 -0400, Jeremy Katz wrote:
Not without doing some sort of hack to precache binaries. Because you
want to eject and then halt. If you have to do
On Tue, 2008-06-10 at 14:45 -0700, Garrett Cooper wrote:
My name is Garrett Cooper and one of the groups I'm a part of at
Cisco is in charge of finding a process management tool in the IOS -
Linux porting project currently in place. upstart is an excellent
candidate for this work.
Nice to
On Thu, 2008-06-12 at 13:54 -0700, Saravanan Shanmugham (sarvi) wrote:
May be a different way to ask this question is would it make sense to
have some of the header files associated with the message/errr
definitions under the upstart directory LGPLed.
This would make it simpler for people
On Fri, 2008-06-13 at 08:20 -0700, Saravanan Shanmugham (sarvi) wrote:
If I had a proprietary program and wanted to talk to Upstart.
Licence your program under the GPL.
Scott
--
Have you ever, ever felt like this?
Had strange things happen? Are you going round the twist?
signature.asc
On Mon, 2008-06-16 at 10:01 -0700, Saravanan Shanmugham (sarvi) wrote:
Found the problem. I needed the gettext-devel package i just had
gettext only.
Might be helpfull to add this to the HACKING notes.
HACKING already contains this:
The source tree for upstart uses the GNU Build System
On Mon, 2008-06-16 at 17:27 -0700, Garrett Cooper wrote:
Correct me if I'm wrong, but this is only for Redhat / Debian based
distros. Some other distros [built from source] like Gentoo Linux
don't suffer from this -devel-ness, so this is a distro specific
note I think...
Only RedHat-based
Hey folks,
A short while ago, the development branches of Upstart and libnih got
renamed again when my Launchpad username changed. Since nobody has
screamed, I suspect everyone did the right thing, if not, here's two
easy commands to get back:
bzr pull --remember lp:libnih
bzr pull
On Wed, 2008-06-18 at 15:06 -0700, Garrett Cooper wrote:
Maybe where my wonderment comes from is will all apps that
previously were just able to communicate with sysv
Which applications were those? ;-)
sysvinit never had a documented IPC protocol.
Scott
--
Have you ever, ever felt like
On Wed, 2008-06-18 at 15:21 -0700, Garrett Cooper wrote:
Would the definition of simple case be a straight up SIGCHLD?
If the process dies, Upstart will receive SIGCHLD, and if marked
respawn it will be restarted.
Detecting things like a stoned process is more interesting.
You'd want to do
On Thu, 2008-06-26 at 05:26 -0700, Garrett Cooper wrote:
LTP has a number of whitebox and blackbox tests in place [3],
most of the whitebox tests being C API's and the blackbox tests being
shell invocations of Unix commands, as well as a well-defined set of
test reporting API's and
On Tue, 2008-07-29 at 11:59 -0700, Saravanan Shanmugham (sarvi) wrote:
What is the plan for System Events in Upstart.
What I mean by System Events are things like
1. registering and receving notifications filesystem changes
through inotify.
Most likely received via D-Bus from a
On Fri, 2008-07-18 at 23:09 +0200, Arnaud Quette wrote:
next, a personal point of view about the lack of upstream adoption of
upstart:
I wanted to provide an upstart script for NUT for some time, but never
found enough matching example to do so.
the embedded scripts only address inittab, and
I know you've all been waiting a while, but finally 0.5 is considered
stable enough for a release. This supersedes 0.3 as the supported
series, while trunk will now begin work on 0.10
Special thanks to Casey and Johan for their help.
0.5.0 2008-08-12 One of those deaf-mutes
* The
On Tue, 2008-09-09 at 02:36 -0700, Saravanan Shanmugham (sarvi) wrote:
I was looking into the NIH DBus binding generation tool that are
used in the development of initctl.
I am working on adding an UpstartInit client library section to the
Upstart code so that it gets built and installed
On Thu, 2008-10-30 at 20:16 -0700, Garrett Cooper wrote:
Just doing some more testing and while I understand while this would
most likely not work, I'm still wondering if it's documented or not:
Assuming that you mean that the environment of the child scripts doesn't
affect the job, that's a
On Tue, 2008-11-04 at 14:31 +0100, Matthias Urlichs wrote:
Scott James Remnant:
The idea would be that when the pre-start script exits, we pick up the
environment table and add that back to the job -- this may require some
changes to the way init gets child signals or something though
This thread made me realised that I've not really discussed the 0.10
plans yet, so seems as good a time as any. This is all still rough
draft at the moment, so forgive any hand-waving and please feel free to
jump in.
Jobs, States and Events are separate; but connected.
A Job can be defined
On Thu, 2008-11-06 at 17:40 +0100, Harald Hoyer wrote:
Why do you want to disable it?
e.g. I don't want to remove the rpm package, but I want all scripts
with
/sbin/start service-xyz to fail.
But *why* do you want that?
I prefer to consider actual use cases and examples to understand
On Thu, 2008-11-06 at 18:27 +0100, Harald Hoyer wrote:
Because, I don't want a service to start (neither automatically by
upstart nor on demand).
Ok, as long as a package update does not reinstall the job file, I can
just move it away.
But *why* do you want this?!
Give an example of a
On Thu, 2008-11-06 at 10:45 -0500, Casey Dahlin wrote:
I've written a prototype for a service state machine which will
hopefully behave more simply and cleanly than the present event-driven
upstart. I'm posting it here for general comments. Its written in ruby
and consists of the
On Thu, 2008-11-06 at 19:46 +0100, Harald Hoyer wrote:
I mean a system service (like sendmail) which is defined as a daemon
in a job file.
Now, I temporarily want to disable sendmail without removing the whole
sendmail package.
In this instance, you presumably want it not automatically
On Fri, 2008-11-07 at 15:47 +0100, Michael Biebl wrote:
2008/11/7 Scott James Remnant [EMAIL PROTECTED]:
On Fri, 2008-11-07 at 14:06 +0100, Michael Biebl wrote:
2008/11/7 Scott James Remnant [EMAIL PROTECTED]:
In the 0.10 design, this is supported by adding a stanza like
manual
On Fri, 2008-11-07 at 08:48 -0500, Charlie Woloszynski wrote:
I think perhaps the state of the jobs could be persisted and restored
on reboot (as an option). If someone did a 'upstart stop-persistently
sendmail' then upstart would know to not just stop sendmail for the
time being but
To kick start the journey towards 0.10, here's a new release; it mostly
just updates the code to adopt the new allocator, which is a good first
step.
I hope to make regular releases throughout the 0.10 process, some of
them may be quite boring like this one; others may be so exciting,
you'll
On Thu, 2009-02-12 at 16:23 -0800, Garrett Cooper wrote:
I found this gem while producing tests for upstart, and I'm
wondering whether or not this is a bug that should be filed:
[comet-k5-12:/etc/init/jobs.d]$ cat foo+
stop on halloween / duwali
[comet-k5-12:/etc/init/jobs.d]$ start
On Fri, 2009-02-13 at 10:30 -0800, Garrett Cooper wrote:
On Fri, Feb 13, 2009 at 10:23 AM, Scott James Remnant
sc...@netsplit.com wrote:
On Thu, 2009-02-12 at 16:23 -0800, Garrett Cooper wrote:
I found this gem while producing tests for upstart, and I'm
wondering whether
On Fri, 2009-02-13 at 12:15 -0800, Garrett Cooper wrote:
How are those arguments fed back from the event? Or is it a feature
that's not available yet? I'm confuzzled because I didn't see it in
the documentation :P.
As arguments to initctl emit.
Scott
--
Have you ever, ever felt like this?
On Mon, 2009-02-23 at 13:14 +0100, Mark Rosenstand wrote:
Is this the only thing that keeps upstart from working on non-initrd
systems? Seems it didn't make it into 0.5.1 :(
Nobody has supplied a patch.
Scott
--
Have you ever, ever felt like this?
Had strange things happen? Are you going
On Tue, 2009-02-24 at 08:54 -0500, Steve Grubb wrote:
On Wednesday 14 January 2009 12:48:12 pm Steve Grubb wrote:
I fixed all the issues pointed out in the comments. I will update the
patch and resend soon.
Sorry about the delay...but I think I have it working as you had suggested.
On Tue, 2009-04-14 at 00:42 -0700, Saravanan Shanmugham (sarvi) wrote:
I saw the plan/roadmap presentation for 1.0, but i could not figure
out which branch in lauchpad its being done on.
Hi Sarvi,
I'm developing the next version of Upstart largely in private at the
moment, so you won't
On Thu, 2009-04-30 at 14:47 -0400, Kevin Hunter wrote:
At 4:29am -0400 on Tue, 14 Apr 2009, Scott Remnant wrote:
On Tue, 2009-04-14 at 00:42 -0700, Saravanan Shanmugham (sarvi) wrote:
I saw the plan/roadmap presentation for 1.0, but i could not figure
out which branch in lauchpad its being
On Tue, 2009-05-05 at 15:21 -0400, Casey Dahlin wrote:
In any Open Source project, it's quite normal for a developer to go off
and do their own thing for a while before submitting or landing the
code. This is especially and triply true if they're doing some
fundamental changes and don't
On Fri, 2009-05-22 at 15:47 +0200, Kees Jongenburger wrote:
I created bug https://bugs.launchpad.net/upstart/+bug/337665 for this
but we did not get any feed-back on that so I don't know what to say
about this.
Err, I discussed this extensively on IRC with you.
Upstart is behaving
On Fri, 2009-05-22 at 10:01 -0400, Casey Dahlin wrote:
Scott James Remnant wrote:
Hey folks,
As to the work on changes to Upstart, the first and most important thing
you could do to help is to comment and discuss on my plans. Go watch
the video of the FOSDEM talk I gave earlier
Wikis are bad places to discuss things
Sent from my iPhone
On 22 May 2009, at 16:19, Casey Dahlin cdah...@redhat.com wrote:
Scott James Remnant wrote:
On Fri, 2009-05-22 at 10:01 -0400, Casey Dahlin wrote:
Scott James Remnant wrote:
Hey folks,
As to the work on changes to Upstart
On Tue, 2009-05-19 at 12:47 -0600, Milton Calnek wrote:
I'm trying to port upstart 0.5.1 to CentOS.
I am now at a point where my machine boots, most jobs are starting
properly.
So I can ssh into the box, but the tty's don't take the virtual
consoles... I don't see /etc/issue on the
On Fri, 2009-05-22 at 12:46 -0600, Milton Calnek wrote:
On Fri, May 22, 2009 at 10:25 AM, Scott James Remnant
sc...@netsplit.com wrote:
On Tue, 2009-05-19 at 12:47 -0600, Milton Calnek wrote:
I'm trying to port upstart 0.5.1 to CentOS.
I am now at a point
On Fri, 2009-05-22 at 22:20 +0200, Kees Jongenburger wrote:
On Fri, May 22, 2009 at 3:53 PM, Scott James Remnant sc...@netsplit.com
wrote:
On Fri, 2009-05-22 at 15:47 +0200, Kees Jongenburger wrote:
I created bug https://bugs.launchpad.net/upstart/+bug/337665 for this
but we did
On Sat, 2009-05-23 at 18:24 +0200, Kees Jongenburger wrote:
On Sat, May 23, 2009 at 5:58 PM, Scott James Remnant sc...@netsplit.com
wrote:
On Sat, 2009-05-23 at 09:11 +0200, Kees Jongenburger wrote:
On Sat, May 23, 2009 at 1:02 AM, Scott James Remnant sc...@netsplit.com
wrote
I've updated the text of the ContributingCode page to hopefully get a
better process for making patches visible and getting them reviewed and
accepted faster.
Contributing code to any Open Source project for the first time can be
an exciting, but also nerve-wracking, thing. Each project has
On Sun, 2009-06-14 at 15:57 -0400, Casey Dahlin wrote:
This is my attempt to record and formalize Scott's description to me of
the way Upstart 1.0 should behave. Its not complete and need some
review, but there's a critical mass there now and I think its time to
draw attention to it.
On Tue, 2009-06-16 at 21:45 +0200, Kees Jongenburger wrote:
Thanks Casey for starting this disc
On Sun, Jun 14, 2009 at 9:57 PM, Casey Dahlincdah...@redhat.com wrote:
This is my attempt to record and formalize Scott's description to me of
the way Upstart 1.0 should behave. Its not
And positively frigidly far away from the heels of 0.3.10 comes the 0.5
series release that includes the same bug fix, along with a whole heap
of other changes - mostly D-Bus, but there's a few other bug fixes in
there too.
0.5.2 2009-06-17 Something, something, something, D-Bus
* The
On Wed, 2009-06-17 at 11:33 -0700, Saravanan Shanmugham (sarvi) wrote:
Why the move to GPLv3. I am not sure how many in the community see this
as a problem, but we do.
Canonical's licensing policy is to use whatever licence is currently
recommended by the Free Software Foundation, that is v3
Yes, it is now GPLv3.
If you have a real and valid concern about this, please state it
verbosely in a manner that I can forward to Canonical's legal department
for consideration.
Scott
--
Have you ever, ever felt like this?
Had strange things happen? Are you going round the twist?
On Wed, 2009-06-17 at 09:53 -0700, Daniel L. Miller wrote:
Scott James Remnant wrote:
There as probably much more required methods on_start on_event
on_starting on_failed_dependency ...
Failed dependency is an interesting one; Upstart doesn't really
process jobs in that way
On Thu, 2009-06-18 at 10:06 +0100, Scott James Remnant wrote:
If you had standalone tools/command or utility programs that don't talk
to each other, I suspect it would have been ok.
Upstart is one of those applications that everyone in the system needs
to communicate via D-Bus
On Thu, 2009-06-18 at 14:11 +0100, Adam Sampson wrote:
Scott James Remnant sc...@netsplit.com writes:
* D-Bus 1.2.4 is now required, and must be patched to fix
https://bugs.freedesktop.org/show_bug.cgi?id=22316
That's a pretty old version. More recent stable versions of dbus
Another stable release to fix another crasher, I dunno you wait two
years for a release and then two come along at once!
0.3.11 2009-06-19 For Friday, June 19th 2009, I'm Jon Masters
* Fixed crash when the first job started by an event hits the
respawn limit and frees the
Thanks to everybody who commented on the change of Upstart Licence,
especially those who responded in private to detail their concerns with
version 3 of the GNU General Public Licence.
I appreciate the problems highlighted, and that many of you working in
the embedded community have customers who
On Mon, 2009-07-06 at 17:48 +0300, Иво Георгиев wrote:
Does Upstart support job dependencies and will it support? I mean, for
example, on event runlevel 3, all the jobs for runlevel 3 are
started, but can the job be configured to start on event runlevel 3,
when other job is started. Also, can
At last, the announcement of a new stable series. This one's based off
0.5.2 but with a lot of the sharp corners shaved off, and lots of bug
fixes.
I strongly suggest that everybody using 0.3.x or 0.5.x now bite the
bullet and switch to using 0.6.0, I probably won't make another release
on those
On Tue, 2009-07-14 at 11:12 +0200, Enrico Scholz wrote:
Scott James Remnant scott-Umf49k1wg4FWk0Htik3J/w...@public.gmane.org
writes:
* Configuration paths have changed. Global configuration now
resides in /etc/init.conf while jobs are now configured in
/etc/init
What
Thanks to Jeff Oliver's debugging, I was able to understand why the
ptrace()-based daemon supervision wasn't working half the time and come
up with a simple fix. Having working expect fork and expect daemon
is a big win!
Cleaned up a couple of minor runlevel in sysinit bugs at the same
time; and
On Fri, 2009-07-17 at 15:31 +0200, Enrico Scholz wrote:
is there a way to send a specific signal to a process started by a job?
E.g. something like
initctl kill -USR2 my-job
Not directly like this, however initctl status my-job will tell you
the pid.
Scott
--
Have you ever, ever felt
The biggest disadvantage to people actually using your software is that
they find bugs, this one's a doozy because it looks like it affects
older 0.3 releases as well. Now seems as good a time as any to repeat
my recommendation that distributions, mobile and embedded appliance
developers using
On Wed, 2009-08-12 at 22:31 -0400, Casey Dahlin wrote:
If you are getting failures in the event_new() test case in trunk, or
any of the other constructor test cases due to a parent which was
expected to be NULL, you need to update your libnih. Just a friendly
poke about the gotcha.
On Thu, 2009-08-20 at 20:22 +0200, Kees Jongenburger wrote:
I am trying to cross compile upstart 0.6.3 and am encountering a
problem. The build system uses nih-dbus-tool to generate dbus stubs
and to be able to cross compile I need nih-dbus-tool to be compiled
targeting the host system but
On Tue, 2009-08-25 at 08:43 +0200, Kees Jongenburger wrote:
I've no idea how to do this, but would gladly accept patches - I imagine
that it must be possible with Automake.
The main problem is that I also need to compile nih and nih-dbus
object is a separate directory when compiling the
On Fri, 2009-09-11 at 17:03 -0400, Casey Dahlin wrote:
I've had some suggestions for the Upstart 1.0 design which came up
when I spoke to Scott on IRC the other day. I would like to post them
here, but for continuity's sake, I figured I'd simply post the 1.0
design as Scott described it (and
On Tue, 2009-10-20 at 16:08 +0200, Michael T wrote:
Something that has always annoyed me about traditional init was the fact that
the scripts are kept under /etc, although nowadays they are almost never user
configuration files in the sense that they used to be, but scripts which come
with
On Tue, 2009-10-20 at 17:11 +0200, Michael T wrote:
Do you actually expect that the average user of upstart will modify a
significant percentage of those scripts? If so then putting them in /etc
obviously makes sense.
I don't think that's relevant at all.
If the average user doesn't do it,
On Thu, 2009-10-22 at 14:07 +0300, Janne Karhunen wrote:
On Wed, Oct 21, 2009 at 5:59 PM, Scott James Remnant sc...@netsplit.com
wrote:
Kernel panic - not syncing: Attempted to kill init!
Huh, that's kinda unusual - have you checked whether init is crashing?
Maybe init=/bin/bash
On Fri, 2009-10-30 at 12:10 -0700, Garrett Cooper wrote:
So, I don't see why Upstart shouldn't continue to follow this model,
unless you have a valid concern about the way that the jobfiles are
laid out
More to the point, I've not heard any arguments why Upstart should adopt
a different
On Tue, 2009-11-03 at 08:43 -0600, Bob wrote:
running ubuntu 9.10 64 bit it appears the init process is taking way too
much process and memory
Your supplied output doesn't support this assertion:
1 root 20 0 19432 1732 1188 S0 0.0 0:00.99
init
Total CPU
On Thu, 2009-11-26 at 14:28 +0200, Janne Karhunen wrote:
Finally got around to this. There's a hacky patch attached that
introduces 'reboot' stanza that will issue reboot given that we
hit respawn limit for 'reboot' marked task. While this seems
working, issuing reboot is probably not the
On Tue, 2009-12-01 at 21:46 +0200, Janne Karhunen wrote:
On Tue, Dec 1, 2009 at 8:14 PM, Scott James Remnant sc...@netsplit.com
wrote:
This means that you could just do (as a file in /etc/init):
start on stopped $JOB RESULT=failed PROCESS=respawn
exec /sbin/reboot
On Tue, 2009-12-01 at 22:35 +0200, Janne Karhunen wrote:
Anyhoo, I'll send you setuid / setgid patches next. You
have another hack in your sleeve for those :-) ?
Which were those?
Just a support for defining task uid/gid via stanza.
Will send them soonish unless you have cleverly
On Thu, 2009-12-03 at 16:25 +0200, Janne Karhunen wrote:
On Tue, Dec 1, 2009 at 10:38 PM, Scott James Remnant sc...@netsplit.com
wrote:
I've deliberately omitted this functionality for now, because it's far,
far more complex than just adding a setuid() call to the child process
1 - 100 of 192 matches
Mail list logo
