MobileRead Forums - View Single Post - Koreader running on Kobos (all of them, hopefully!)

NiLuJe · 09-04-2015, 01:59 PM

Meh, it's probably system() and no CLOEXEC biting us in the ass, we're inheriting open fds.

The simplest workaround I can think of is killing WiFi when quitting KOReader, which seems a bit harsh, but would solve this.

(In fact, the startup script does just that when started manually w/ nickel running).

Doing it the right way would mean using CLOEXEC everywhere, which might be easier said than done, and would break compatibility with Linux < 2.6.23 (which, granted, only applies to legacy (non-touch) Kindles and possibly the first gen Kobos).

EDIT²: FreeType should default to using CLOEXEC... If it doesn't, that's probably a ToolChain issue. I don't remember which TC the buildbot is using for the Kobos, I'll launch a build with my own just for shit 'n giggles...

09-04-2015, 01:59 PM	#2370
NiLuJe BLAM! 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	Meh, it's probably system() and no CLOEXEC biting us in the ass, we're inheriting open fds. The simplest workaround I can think of is killing WiFi when quitting KOReader, which seems a bit harsh, but would solve this. (In fact, the startup script does just that when started manually w/ nickel running). Doing it the right way would mean using CLOEXEC everywhere, which might be easier said than done, and would break compatibility with Linux < 2.6.23 (which, granted, only applies to legacy (non-touch) Kindles and possibly the first gen Kobos). EDIT²: FreeType should default to using CLOEXEC... If it doesn't, that's probably a ToolChain issue. I don't remember which TC the buildbot is using for the Kobos, I'll launch a build with my own just for shit 'n giggles... Last edited by NiLuJe; 09-04-2015 at 02:10 PM.