MobileRead Forums - View Single Post

NiLuJe · 11-22-2013, 02:31 PM

@cryzed: KUAL basically does a grep, so, nope, it should track the config properly, no matter what.

The verbose behavior you mention is perfectly normal. Those are the last messages being printed, and nothing will automatically overwrite them, so nothing wrong there. With the notable exception that enabling OpenSSH isn't what triggered the iptables message, enabling WiFi hole-punching is.

The second part would imply that volumd isn't even part of the problem, and that ssd is being dumb with its PID file and/or fails to kill sshd, which is very, very strange... Will check on 5.3.9, just in case [EDIT: Nope, nothing wrong on my end].

What about the usb0 ip warning, does that still happen?

11-22-2013, 02:31 PM	#31
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	@cryzed: KUAL basically does a grep, so, nope, it should track the config properly, no matter what. The verbose behavior you mention is perfectly normal. Those are the last messages being printed, and nothing will automatically overwrite them, so nothing wrong there. With the notable exception that enabling OpenSSH isn't what triggered the iptables message, enabling WiFi hole-punching is. The second part would imply that volumd isn't even part of the problem, and that ssd is being dumb with its PID file and/or fails to kill sshd, which is very, very strange... Will check on 5.3.9, just in case [EDIT: Nope, nothing wrong on my end]. What about the usb0 ip warning, does that still happen? Last edited by NiLuJe; 11-22-2013 at 03:09 PM.