Thread: Glo HD dmesg* and syslog* files
View Single Post
Old 02-29-2020, 02:43 PM   #1
Ripplinger
350 Hoarder
Ripplinger ought to be getting tired of karma fortunes by now.Ripplinger ought to be getting tired of karma fortunes by now.Ripplinger ought to be getting tired of karma fortunes by now.Ripplinger ought to be getting tired of karma fortunes by now.Ripplinger ought to be getting tired of karma fortunes by now.Ripplinger ought to be getting tired of karma fortunes by now.Ripplinger ought to be getting tired of karma fortunes by now.Ripplinger ought to be getting tired of karma fortunes by now.Ripplinger ought to be getting tired of karma fortunes by now.Ripplinger ought to be getting tired of karma fortunes by now.Ripplinger ought to be getting tired of karma fortunes by now.
 
Ripplinger's Avatar
 
Posts: 3,574
Karma: 8281267
Join Date: Dec 2010
Location: Midwest USA
Device: Sony PRS-350, Kobo Glo & Glo HD, PW2
dmesg* and syslog* files

Two files seem to be created every time I turn the reader on or wake it and are stored in the .kobo directory. The file names add the date to them like so:

dmesg-2020.02.29-13.26.15
syslog-2020.02.29-13.26.15

I only noticed them when I finally updated the miniclock to the most current version, but there were 74 of each file name and I've no idea where they're coming from. Debugging is turned off for the miniclock (and I think those files are named differently, and there's no mention of "miniclock" in the logs), so I'm pretty certain that's not the cause.

I do patch though, did I mess up something in a patch maybe? Or is this possibly normal now?
Ripplinger is offline   Reply With Quote