-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
move logs to UMS #3
Comments
It's next to impossible, because we're still alive when Nickel exports it over USBMS... and in fact, we're logging that onboard got unmounted as it is happening ;). So we effectively can't log to USBMS at that moment, because that would be Bad. And, AFAIK, we can't (easily) close the log file before it happens, and then re-open it after. (We might be able to get a hint that things are about to go down with udev events, but that's a huge mess/intrusive, and I don't think the timing plays in our favor here, and even how non-messy it'd be from inside a C app). TL;DR: We can react to it, and it's what we do to handle our inotify watches, but for logging, we'd have to something before the fact, not after ;). So, yeah, I'd like to, but it's a complex beast ;). Hence the option to log to the syslog instead, because at least that's standard (even if it's a ring buffer never making it to disk on Kobo, you can still That doesn't help much until someone comes up with a front-end for logread on device, but, hey :D. |
Although... It's given me a terrible idea: a watch that plays with FBInk, That only helps if KFMon is somewhat functional, though. And it'd make my life easier if FBInk handled linefeeds, but I'm not sure if I want to mess with the line-breaking/formatting code again... :D. |
Thanks for the (verbose) feedback 👍 And nice tool this fbink of yours 😃 I think it would fit in koreader. Since the last time I checked they bundled dropbear, so I think add a few kbs more isn't a problem. |
Verbose is my middle name ;p. If/Until I manage to get linefeeds handled in a satisfying way, 05d9bf8 implements a massively crappy workaround to do the job ;). As for KOReader, one actual use-case would be progress feedback when uncompressing updates, like I implemented on Kindle via eips. |
Well, it's not too bad... There's a bit of a race between the reader and FBInk for who gets to draw first, but right now, and possibly because it's an image, the reader does another refresh a few seconds after opening, so you get the gist of it magically reappearing. Plus, that leaves you time to admire my awesome handcrafted icon. :D. |
Noope, not a race at all, turned out to be good old I/O buffering. |
Now that 1.2.0 is finally out, that's probably as good as handling this is going to get ;). |
In case you really need logs on the userstore, one possibly alternative may be:
in combined with
in Since that dumps both dmesg & the syslog in |
Hi @NiLuJe, thank you for your work on kfmon. Everything works as expected 😄
I wonder if the logfile can be stored under /mnt/onboard/.adds/kfmon to be able to read it from the computer. This can be handy for new users without ssh connection.
The text was updated successfully, but these errors were encountered: