On Thu, 2019-11-28 at 09:32 +0100, Lennart Poettering wrote:
> On Mi, 27.11.19 14:26, Philip Withnall (phi...@tecnocode.co.uk)
> wrote:
>
> > > > If I were to implement this as a separate daemon, it would need
> > > > to
> > > > be
> > > > active all the time, listening to
> > > >
On Thu, Nov 28, 2019 at 1:32 AM Lennart Poettering
wrote:
>
> Ideally we wouldn't even come up with our own file format for these
> ring buffers, and just use what is already established, but afaiu
> there's no established standard for time series ring buffer files so
> far, hence I figure we
On Mi, 27.11.19 14:26, Philip Withnall (phi...@tecnocode.co.uk) wrote:
> > > If I were to implement this as a separate daemon, it would need to
> > > be
> > > active all the time, listening to
> > > UnitNew/UnitRemoved/JobNew/JobRemoved
> > > signals from systemd. That seems like a waste of a
Hey,
On Tue, 2019-11-19 at 10:26 +0100, Lennart Poettering wrote:
> On Fr, 08.11.19 11:15, Philip Withnall (phi...@tecnocode.co.uk)
> wrote:
>
> > Hello all,
> >
> > As part of work on a GNOME feature for monitoring how often the
> > user
> > uses applications (for example, to let them know
On Fr, 08.11.19 11:15, Philip Withnall (phi...@tecnocode.co.uk) wrote:
> Hello all,
>
> As part of work on a GNOME feature for monitoring how often the user
> uses applications (for example, to let them know that they spent 4
> hours in the Slack app, or 17 hours playing games), I’m trying to
Hello all,
As part of work on a GNOME feature for monitoring how often the user
uses applications (for example, to let them know that they spent 4
hours in the Slack app, or 17 hours playing games), I’m trying to work
out the best way to store data like that.
If we assume the system is using
