View Single Post
Old 06-19-2020, 03:05 PM   #19
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
That's because your NM entry was not quite right.

It's documented in the OCP configs, and in the wiki .

----

To expand on that: both cmd_spawn and cmd_output are *already* passed to sh -c internally, so that was useless. As was redirecting the output, because it's a cmd_spawn, not a cmd_output.

Given the sh -c thing, I do recommend using cmd_spawn & exec to avoid one layer of shell wrapper (and get a mostly-useful PPID (1, because it's reparented to init) in the process, instead of a random sh process).

But, most importantly, use absolute paths. That's what was breaking OTAs. In fact, I'm not quite sure why it wasn't breaking startup, period.

Last edited by NiLuJe; 06-19-2020 at 03:11 PM.
NiLuJe is offline   Reply With Quote