<astr>
whitequark, I've had a ID10T moment. it was the option I had added to fstab. stupid error msg miss lead me. sorry and thank you
<whitequark>
great
xiangfu has joined #qi-hardware
rejon has joined #qi-hardware
atommann has joined #qi-hardware
xiangfu has quit [Quit: leaving]
rejon has quit [Read error: Connection reset by peer]
astr has quit [Ping timeout: 264 seconds]
rejon has joined #qi-hardware
astr has joined #qi-hardware
mooseboobs has quit []
jluis has joined #qi-hardware
jluis has quit [Remote host closed the connection]
Haswell has joined #qi-hardware
pcercuei has joined #qi-hardware
<larsc>
any upstart experts around? I have a plain old init script in /etc/init.d/. It gets properly launched on system start, so far no problem. But it gets also launched when a user logs in and I don't want that
viric has quit [Ping timeout: 264 seconds]
viric has joined #qi-hardware
<DocScrutinizer05>
errrr
<DocScrutinizer05>
I _think_ every init.d/skipt needs a events.d/stub to call it. In such stub there's some line like "on <event>" (iirc) that defines when that stub gets executed by upstart daemon
<DocScrutinizer05>
or maybe like "start on <event>"
<DocScrutinizer05>
lemme check
<DocScrutinizer05>
/etc/event.d/console
<DocScrutinizer05>
start on USER
<DocScrutinizer05>
start on ACT_DEAD
<DocScrutinizer05>
there must be a script that calls init.d scripts
<DocScrutinizer05>
here's one
<DocScrutinizer05>
/etc/event.d/fmtx
<DocScrutinizer05>
description "Starts the FMTX-daemon" start on started hildon-desktop