2014-11-19 00:01 pcercuei has quit [Ping timeout: 264 seconds] 2014-11-19 01:29 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 2014-11-19 01:30 great 2014-11-19 02:20 xiangfu has joined #qi-hardware 2014-11-19 02:43 rejon has joined #qi-hardware 2014-11-19 02:49 atommann has joined #qi-hardware 2014-11-19 02:57 xiangfu has quit [Quit: leaving] 2014-11-19 03:12 rejon has quit [Read error: Connection reset by peer] 2014-11-19 03:23 astr has quit [Ping timeout: 264 seconds] 2014-11-19 03:28 rejon has joined #qi-hardware 2014-11-19 03:37 astr has joined #qi-hardware 2014-11-19 04:11 mooseboobs has quit [] 2014-11-19 07:32 jluis has joined #qi-hardware 2014-11-19 07:57 jluis has quit [Remote host closed the connection] 2014-11-19 07:57 Haswell has joined #qi-hardware 2014-11-19 08:51 pcercuei has joined #qi-hardware 2014-11-19 09:06 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 2014-11-19 09:11 viric has quit [Ping timeout: 264 seconds] 2014-11-19 09:15 viric has joined #qi-hardware 2014-11-19 09:16 errrr 2014-11-19 09:17 I _think_ every init.d/skipt needs a events.d/stub to call it. In such stub there's some line like "on " (iirc) that defines when that stub gets executed by upstart daemon 2014-11-19 09:19 or maybe like "start on " 2014-11-19 09:19 lemme check 2014-11-19 09:20 /etc/event.d/console 2014-11-19 09:21 start on USER 2014-11-19 09:21 start on ACT_DEAD 2014-11-19 09:21 there must be a script that calls init.d scripts 2014-11-19 09:22 here's one 2014-11-19 09:22 /etc/event.d/fmtx 2014-11-19 09:23 description "Starts the FMTX-daemon" start on started hildon-desktop 2014-11-19 09:23 2014-11-19 09:23 stop on starting shutdown 2014-11-19 09:23 exec /etc/init.d/fmtx start 2014-11-19 09:24 larsc: ^^^ 2014-11-19 09:26 http://pastebin.com/HiRf9nK8 2014-11-19 10:22 nicksydney has joined #qi-hardware 2014-11-19 10:33 atommann has quit [Quit: Leaving] 2014-11-19 10:51 wolfspraul has joined #qi-hardware 2014-11-19 10:52 arhuaco has quit [Read error: Connection reset by peer] 2014-11-19 10:53 arhuaco has joined #qi-hardware 2014-11-19 11:22 jluis has joined #qi-hardware 2014-11-19 12:17 viric has quit [Read error: Connection reset by peer] 2014-11-19 12:17 viric has joined #qi-hardware 2014-11-19 12:38 mooseboobs has joined #qi-hardware 2014-11-19 12:39 mooseboobs has quit [Client Quit] 2014-11-19 13:01 infobot has quit [Read error: Connection reset by peer] 2014-11-19 13:02 infobot has joined #qi-hardware 2014-11-19 13:04 ysionnea1 is now known as ysionneau 2014-11-19 13:40 jluis has quit [Ping timeout: 264 seconds] 2014-11-19 14:23 jluis has joined #qi-hardware 2014-11-19 15:38 arhuaco has quit [Ping timeout: 250 seconds] 2014-11-19 15:51 arhuaco has joined #qi-hardware 2014-11-19 17:32 mooseboobs has joined #qi-hardware 2014-11-19 17:57 pcercuei has quit [Ping timeout: 240 seconds] 2014-11-19 20:19 wolfspraul has quit [Quit: leaving] 2014-11-19 21:19 pcercuei has joined #qi-hardware 2014-11-19 22:06 Haswell has quit [Quit: Saliendo] 2014-11-19 22:36 pcercuei has quit [Ping timeout: 245 seconds] 2014-11-19 23:00 nicksydney has quit [Remote host closed the connection] 2014-11-19 23:15 freespace has quit [Ping timeout: 264 seconds] 2014-11-19 23:57 freespace has joined #qi-hardware