Hi all. I am experiencing a little problem with Tomato RAF's logs. Quite sure it's a common code so I'm posting it here. I wrote some scripts that look for something in the log file (/var/log/messages) using awk, the space as a separator, and doing some kind of print $n. This procedure seemed reliable and universally accepted to me, if I'm not proven to be wrong... The problem with Tomato is sometimes logs have an additional space after the month: example of normal behaviour Code: Jan 13 11:09:39 TOMATO daemon.info dnsmasq: read /etc/hosts - 17 addresses example of weird behaviour: Code: Jan 6 15:47:37 TOMATO daemon.info dnsmasq: read /etc/hosts - 5 addresses Please see the double space after Jan. That is a big matter, all the scripts will just not work because there's an additional variable there and all the positions hard-coded should now be shifted (+1). Is this normal/expected? Or is my method plain wrong? If the method is correct I should do another really silly check if the second print $2 is a space (or empty string) and then change all the positions accordingly, but that highly seems a non-standard method to me... Thank you.