**** BEGIN LOGGING AT Sat Nov 03 02:59:58 2018 Nov 03 05:39:13 Tofe: All systemd bits come from https://github.com/webosose/webos-initscripts/blob/master/files/systemd/services/common/activitymanager.service Nov 03 05:39:27 They have a central repo for systemd we have them in the component Nov 03 05:39:32 Morning BTW Nov 03 06:56:13 Tofe: THey have this for which I wonder why: https://github.com/webosose/webos-initscripts/tree/master/src Nov 03 06:56:20 It's some kind of custom init Nov 03 06:56:26 Not sure why they have it Nov 03 06:56:31 JaMa said something about it Nov 03 06:56:46 Basically because they were in the middle between upstart and systemd I think Nov 03 06:58:50 There mus tbe something in logs Nov 03 07:07:19 Morning! Nov 03 07:07:36 Herrie|2: Ah ok, I had forgotten they had a central repo for the services... Nov 03 07:08:32 yes I remember JaMa saying they still had some remaining little bits in upstart Nov 03 07:12:27 Herrie|2: ok, it seems it's pointing in the right direction: https://github.com/webosose/webos-initscripts/blob/master/src/initctl/InitCtl.cpp#L30 Nov 03 07:20:32 Tofe: I did https://github.com/herrie82/webos-initscripts/tree/webosose Nov 03 07:21:37 But seems upstream had quite some changes since Nov 03 07:21:48 I'm not thrilled by the idea of putting back the service files in there Nov 03 07:22:25 Me neither Nov 03 07:22:42 ah you removed nearly everything, I see :) Nov 03 07:22:48 That's why I made a minimal webos-initscripts repo above Nov 03 07:22:55 But might need rebasing Nov 03 07:23:00 And adding back to the build Nov 03 07:26:44 I still don't see where initctl is executed, but I'm still digging Nov 03 07:28:54 https://github.com/webosose/bootd/blob/e5cc02571c464aef785749f840e77ebcdb77cf58/src/bootd/core/SignalManager.cpp#L72 Nov 03 07:28:58 Bootd it seems? Nov 03 07:30:31 oh gosh, well seen Nov 03 07:31:14 And then stuff like: https://github.com/webosose/db8/blob/14aeeb5a8b5fa796e5c837a56f9ba0ee1df06fbb/files/sysbus/dynamic/com.palm.tempdb.service.in#L18 Nov 03 07:31:23 https://github.com/webosose/db8/blob/14aeeb5a8b5fa796e5c837a56f9ba0ee1df06fbb/files/sysbus/dynamic/com.webos.epgdb.service.in#L18 Nov 03 07:31:33 Seems it's just one shots to trigger a signal Nov 03 07:31:51 bootd was actually my missing piece Nov 03 07:32:07 I was still tracking how activitymanager got started Nov 03 07:33:20 but it's bootd, which handles a state machine for the init, and emits signals via initctl. In this case, it triggers webos-rgd.targets, which wants activitymanager. Nov 03 07:33:47 webos-rbd* Nov 03 07:33:56 (rest boot done) Nov 03 07:34:11 I remember I got them to work mostly but it gave soem headaches Nov 03 07:35:35 yes, and it's frustrating because it shouldn't even be needed, thanks to systemd Nov 03 07:41:02 Yes Nov 03 07:56:46 What I understood is that internally some product lines still had upstart that's why they have this Nov 03 07:56:49 But far from ideal Nov 03 08:18:29 upstart (as a init) now isn't used anywhere internally, but initctl is still used by some internal systemd services :/ Nov 03 08:19:20 and instead of fixing those few services to talk with systemd directly, they decided to keep initctl for backwards compatibility Nov 03 09:02:46 JaMa: I understand. It's a pity, because the effort needed to migrate the 6-7 remaining ones isn't that huge Nov 03 09:03:18 Maybe, if we make it work with systemd-only, it'd help push them in that direction ? They would just have to replicate our migration Nov 03 10:06:16 I think I'll need to draw the state machine of these little bits if I don't want to do too many mistakes :) Nov 03 10:43:27 Tofe: If I remember correctly we only trigger a few Nov 03 10:43:34 Others don't exist in OSE source code Nov 03 10:50:03 right; well, the issue here is that we actually don't trigger anything: none of the targets are wanted by anyone Nov 03 10:50:21 I made them all wanted by multi-user.target, that should help :) Nov 03 10:53:41 As for bootd's sequence, it's dead simple: everything is started simultaneously. Nov 03 10:55:49 ok, better ! Nov 03 10:56:19 I now have mojodb, activitymanager... it feels like we're going somewhere. Nov 03 10:56:30 I'll try a global reflash Nov 03 10:57:43 ah, no, one missing piece: we don't detect the end of first use app Nov 03 11:29:42 Tofe: It could be they changed the detection of that in activitymanager of OSE Nov 03 11:29:49 ran-first-use I think we have Nov 03 11:33:14 yep Nov 03 11:33:20 the file is there... Nov 03 11:51:33 Tofe: Configurator should pick that up Nov 03 11:51:49 At least in OWO: https://github.com/openwebos/configurator/blob/18ebce9af19d635b9c8765c7165d2ac2e7b007d0/src/ActivityConfigurator.cpp Nov 03 12:35:26 it still does: https://github.com/webosose/configurator/blob/master/src/ActivityConfigurator.cpp#L101 Nov 03 13:11:26 ah, ok, I don't have /var/luna/preferences/first-use-profile-created Nov 03 13:15:15 ... which should be created there https://github.com/webOS-ports/app-services/blob/webOS-ports/master/com.palm.service.accounts/files/etc/event.d/createLocalAccount#L10 Nov 03 13:16:03 (if the service is launched at all, of course) Nov 03 13:17:15 ah "Not permitted to send to com.palm.tempdb", that's a good hint Nov 03 13:18:30 ooh but that's the famous ' ls-hubd LSHUB_ROLE_FILE {} Can not find service "" permissions for executable "/usr/bin/node" ' Nov 03 13:19:02 ok, let's fix run-js-service Nov 03 13:25:54 That will help Nov 03 13:26:02 You know now how to do that one I saw :P Nov 03 13:26:39 yes, though I'm not sure about this /usr/bin/node Nov 03 13:30:07 run-js-service comes from mojoservicelauncher: https://github.com/openwebos/mojoservicelauncher Nov 03 13:30:38 I guess you might want to check: https://github.com/webosose/mojoservicelauncher/pull/1 Nov 03 13:32:26 possibly! Nov 03 13:36:20 I'm only half here, so try to put some pointers when I get a chance Nov 03 13:36:23 Some might be of help Nov 03 13:41:33 it might help, but it doesn't solve the current issue Nov 03 13:42:28 basically "run-js-service -n /usr/palm/services/com.palm.service.accounts" isn't seen like a web service on the ls-hubd side Nov 03 13:45:15 And if you run others that use run-js-service Nov 03 13:45:16 ? Nov 03 13:45:45 There are some examples in: https://github.com/search?q=org%3AwebOS-ports+run-js-service&type=Code Nov 03 13:46:24 Or better from OSE: https://github.com/search?q=org%3AwebOSose+run-js-service&type=Code Nov 03 13:47:21 There's some more documentation at https://github.com/webosose/nodejs-module-webos-service Nov 03 13:47:25 On how this should work Nov 03 13:49:05 This syntax is funny and uncommon with all the params: https://github.com/webosose/webos-initscripts/blob/3f2a763f5441f306b44d0ad36e271e322cd130e1/files/systemd/services/common/second-screen-gateway.service#L30 Nov 03 13:52:12 let me try a bit Nov 03 13:55:20 I get the same kind of LS2 errors about service "" for node not found, though the service itseslf didn't seem to complain. But maybe devmode doesn't do much :) Nov 03 16:30:31 EricBlade: ah, maybe you would be able to help ? I am trying to have run-js-service on top of webOS OSE, but it doesn't seem to work well Nov 03 16:31:46 Basically, I think the issue sums up to ls-hubd not understanding that com.palm.service.accounts started this way is a web service Nov 03 16:35:09 But I'm not sure what ultimately does the distinction between a web service and the "/usr/bin/node" app Nov 03 17:31:53 Tofe: Going by EricBlade's Twitter he was enjoying the casino, so might be away for the weekend ;) Nov 03 17:32:04 He's a pretty decent poker player from what I understood Nov 03 17:32:38 :) ok **** ENDING LOGGING AT Sun Nov 04 02:59:59 2018