journalctl --list-boots seems great actually but wouldn't work for us. We cannot keep lots of logs in our products.
Ultimately we are trying to answer the question of how long one of our product has been in use. We will implement it with a .timer/.service which periodically adds /proc/uptime to a file and the file gets preserved over reboot. Umut On Mon, Nov 2, 2015 at 7:00 PM, Lennart Poettering <lenn...@poettering.net> wrote: > On Mon, 02.11.15 15:46, Umut Tezduyar Lindskog (u...@tezduyar.com) wrote: > >> Hi, >> >> We would like to implement a feature to keep track of accumulated >> values of uptimes in our products. Tracked time will give us the total >> usage time of our product not just since last reboot (/proc/uptime). >> >> Is upstream interested in having such implementation? > > As Dimitri suggested: wouldn't a journalctl --list-boots invocation > suffice for this? > > Or do you need this per-service? (where the journal should be able to > provide you with the answer too, of course, but with a different line) > > Lennart > > -- > Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
