One thing I was wondering about was, on a headless system, but that does have an LCD display, is maybe capturing the progress of procd as it runs and displaying it on that LCD.
Looking at /var/log/messages, I see: 2017-02-12T05:49:52+00:00 Powercode kernel: 4.660666] procd: - early - 2017-02-12T05:49:52+00:00 Powercode kernel: 5.253264] procd: - watchdog - 2017-02-12T05:49:52+00:00 Powercode kernel: 5.256546] procd: - ubus - 2017-02-12T05:49:52+00:00 Powercode kernel: 5.323323] procd: - init - 2017-02-12T05:50:28+00:00 Powercode procd: - init complete - and I see where those are generated in the procd source. I don’t see where procd communicates (logs) it’s progress that we could attach an observer. Maybe in q_initd_run() where the DEBUG(2, “start %s %s \n”…) happens, and in q_initd_complete() where the DEBUG(2, “stop %s %s \n”, …) happens? Hmm… for that matter, I also don’t know where procd does a wait() or wait3() or waitpid() on the rc.d/ scripts... I’m not sufficiently versed in procd to guess at how to go about this. Anyone else know? Thanks, -Philip _______________________________________________ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
