Problems writing an upstart job

Scott James Remnant scott at netsplit.com
Mon Dec 14 07:23:12 GMT 2009


On Thu, 2009-11-19 at 23:02 +0100, Wolfgang Holoch wrote:

> First steps
> At first I tried a upstart configuration like that:
> ====================================
> start on starting gdm
> script
> 	# ...
> end script
> ====================================
> because I thought that would be sufficient, but it did not work. I
> always got an error message in my syslog like that:
> "initgb main process (2733) terminated with status 1"
> and the script did not changed anything as expected.
> 
A good way to debug these things is to add "console output" to the job,
and "set -x" inside the script stanza - then you'll find out which part
of your script is failing.

> Further steps
> I also tried "start on startup" but with the same result, then I tried
> some further stuff but without success. I am also a little bit confused
> about the event "graphics-device-added" which is noticed in the gdm.conf
> file but I did not found any clue where this event is coming from.
> 
graphics-device-added is an event that comes from udev (via the upstart
bridge), it corresponds to an ACTION=add SUBSYSTEM=graphics uevent from
the kernel.

Scott
-- 
Have you ever, ever felt like this?
Had strange things happen?  Are you going round the twist?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/upstart-devel/attachments/20091214/5c8630ff/attachment.pgp 


More information about the upstart-devel mailing list