On Tue, Nov 03, 2015 at 07:27:39AM +0100, Umut Tezduyar Lindskog wrote:
> 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.
>
On Tue, Nov 3, 2015 at 1:20 PM, Dimitri John Ledkov
wrote:
> On 3 November 2015 at 06:27, Umut Tezduyar Lindskog wrote:
>> journalctl --list-boots seems great actually but wouldn't work for us.
>> We cannot keep lots of logs in our products.
>>
>
>
On 3 November 2015 at 06:27, Umut Tezduyar Lindskog wrote:
> journalctl --list-boots seems great actually but wouldn't work for us.
> We cannot keep lots of logs in our products.
>
You shouldn't need to keep lots of logs, just a timer unit that would
query and store/transmit
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?
Umut
On 2 November 2015 at 14:46, Umut Tezduyar Lindskog 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).
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).
>
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