MobileRead Forums - View Single Post

NiLuJe · 09-29-2019, 10:40 PM

@davidfor: Oh. USB. That would certainly explain it. Thanks

.

Random thought: 512KB might be the actual size of the syslog ringbuffer, which is why I usually follow it somewhere when I'm not sure if I'm going to have enough backlog in a single "after the fact" logread call

.

(In practice, that usually involves a logread -f in a shell over USBNet, or over WiFi w/ ForceWifiOn for USB-related stuff).

09-29-2019, 10:40 PM	#10
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	@davidfor: Oh. USB. That would certainly explain it. Thanks . Random thought: 512KB might be the actual size of the syslog ringbuffer, which is why I usually follow it somewhere when I'm not sure if I'm going to have enough backlog in a single "after the fact" logread call . (In practice, that usually involves a logread -f in a shell over USBNet, or over WiFi w/ ForceWifiOn for USB-related stuff). Last edited by NiLuJe; 09-29-2019 at 10:44 PM.