[13:53] <djszapi> How can I run an upstart script manually for testing purpose ?
[14:40] <ion> It’s not a script, and “start jobname”.
[14:52] <djszapi> ion: well, something is wrong :(
[14:53] <djszapi> exec /usr/sbin/start-cupsd.sh -> I try to run this custom file from an upstart job
[14:53] <djszapi> Which is intended to run this script: http://paste.kde.org/73711/
[14:54] <djszapi> and 1) I do not see the created directory 2) cups daemon is not run at all
[14:54] <djszapi> how could I debug the issue ?
[14:55] <djszapi> http://paste.kde.org/73717/ -> this is my apps/cups.conf
[16:26] <djszapi> When are the /etc/init/apps/ jobs run ?
[16:40] <jhunt> djszapi: take a look at http://upstart.ubuntu.com/cookbook/#debugging
[18:21] <SpamapS> Hrm.. so we're hitting the "state problem" again with network-manager. It needs to not stop until after a certain event has run. But right now it is 'stop on stopping dbus' .. so if I make it 'stop on stopping dbus and deconfiguring-networking' .. 'stop dbus' will hang. ... 
[18:30] <SpamapS> so I almost have to make dbus have a dbus-shutdown.conf that works like portmap-boot.conf and identifies itself as specifically the dbus that stops on runlevel [06]
[18:31] <SpamapS> s/almost/think I probably/
[19:53] <SpamapS> hmm.. unless I just make dbus stop on my new event