Hi,
Really appreciate your great work!
I have a question during greping "AddMatch" in the code: I see there are 2
`AddMatch` method calls sent to the bus, but I can't find the place to handle
this signal. Could you point me out the place it is handled? Thanks!
Another question is, how can I
On Thu, Dec 22, 2022, at 11:00 AM, Lennart Poettering wrote:
> On Do, 22.12.22 10:56, Chris Murphy (li...@colorremedies.com) wrote:
>> Still another idea, we could add a new setting MinRetentionSec=90day
>> which would translate into "not less than 90 days" and would only
>> delete journal
On Do, 22.12.22 10:56, Chris Murphy (li...@colorremedies.com) wrote:
> The consensus of the discussion is that there should be less
> retention. The range of retention varies quite a bit, but I think
> 3-6 months is OK.
Sounds OK to me.
> Still another idea, we could add a new setting
Hi,
Fedora Workstation working group is considering reducing the journal retention
policy from upstream default.
This is the tracking issue
https://pagure.io/fedora-workstation/issue/213
This is the Fedora development list discussion thread
On Thu, Dec 22, 2022 at 08:00:06PM +1100, Michael Chapman wrote:
> On Thu, 22 Dec 2022, Andrei Borzenkov wrote:
> > On Thu, Dec 22, 2022 at 11:17 AM Nicolas Pillot
> > wrote:
> > >
> > > Hello
> > >
> > > I am wondering if i can dynamically plan jobs (once) using systemd timer.
> > > What i mean
On Thu, 22 Dec 2022, Andrei Borzenkov wrote:
> On Thu, Dec 22, 2022 at 11:17 AM Nicolas Pillot
> wrote:
> >
> > Hello
> >
> > I am wondering if i can dynamically plan jobs (once) using systemd timer.
> > What i mean by that is kind of replicating the usage of the 'at' command
> >
>
>
On Thu, Dec 22, 2022 at 11:17 AM Nicolas Pillot
wrote:
>
> Hello
>
> I am wondering if i can dynamically plan jobs (once) using systemd timer.
> What i mean by that is kind of replicating the usage of the 'at' command
>
systemd-run --on-calendar=tomorrow echo I am at replacement
> If not,
Hello
I am wondering if i can dynamically plan jobs (once) using systemd timer.
What i mean by that is kind of replicating the usage of the 'at' command
If not, could i maybe use a user timer unit, triggering a script which as a
last action would delete said unit ?
or should i simply stick to
