2014-09-03 The magazine is finished; I'm pleased with the result. Now, afterwards, I wanted to know how much time I had spent working on it. As I used the machine only for the work on the magazine and had it only running when I worked on it, the boot times should give me a good estimate. On other machines, I have `uptimed' installed, on this one unfor- tunately not. But there's a standard tool as well: last(1). `last reboot' prints out the reboot times of the current wtmp log. The log rotates monthly, hence I used `last -f /var/log/wtmp.1 re- boot' as well. One system uptime reached over the log rotation. In consequence, the last entry was never closed. This lead to some confusion. Us- ing the `-F' switch cleared it up, because it printed the dates was well as the times. But when did I shut the system down that night? Sadly, the wtmp log file is binary, otherwise I could have simply looked at the source data. Instead I used `stat /var/log/wtmp.1'. The Change Date seems to be the time of the shutdown. It's plausible, at least. And it is not the time of the logrotaion, because cron.daily runs at a different time on that machine. Funny thread in dfde: Someone wanted to search for Linefeeds in text files. [0] Actually, every text file in Unix should have at least one Linefeed (i.e. ``Newline''). Grepping for them is a bit ridiculous: `grep \$'. (Of course, his question was meant a bit differently, but treating it this way was more fun.) [0] https://debianforum.de/forum/viewtopic.php?f=34&t=151129 http://marmaro.de/lue/ markus schnalke