On Thu, 11.10.12 01:48, Lennart Poettering (mzerq...@0pointer.de) wrote: > On Wed, 10.10.12 16:50, Kevin Fenzi (ke...@scrye.com) wrote: > > > "My laptop started acting up last tuesday, I should see whats in the > > logs from then" > > > > "I'd like to run a daily report on my logs" > > These two are much better implemented via explicit time seeks. The > journal APIs support that just fine, journalctl currently > doesn't. However it's trivial to add that based on the lower level APIs, > the only thing that stopped me from doing that so far is that for that > we'd have to come up with a nice way to parse calendar timestamps, and I > want to be careful about that. that said the idea is to have two command > line args to journalctl where you can pass things such as: > > $ journalctl --start-time=2012-10-01 > ... > $ journalctl --start-time=-5d > ... > $ journalctl --start-time=2012-01-01 --end-time=2012-05-02 > ...
A quick update: This is implemented now, but I called it --since= and --until=. I'll push this into F18 as well, sicne it's actually a minor change only, and just too useful. Lennart -- Lennart Poettering - Red Hat, Inc. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
