Sven Hartge <s...@svenhartge.de> writes:

> Mart van de Wege <m...@vdwege.eu> wrote:
>
>> Nope, not ephemeral at all, it's PID 1. Since I don't have timers
>> running this job, apparently there's a zombie process somewhere?
>
> PID 1 hints at a systemd.timer, even if you have dismissed this
> previously. Also the start time of just after midnight hints at this.
>
> And when I look at the current btrbk package in Sid/Testing I do indeed
> see it ships a timer in /usr/lib/systtemd/
>
> So, there is your answer then.

Well whaddayaknow. I hadn't checked the system timers under
/usr/lib/systemd/

And that is the bastard running the ghost job.

Surely packaging a system timer file like that should not be done? It
should be at the discretion of the admin to create one if they want to
run btrbk on a schedule.

Regards,

Mart

-- 
"We will need a longer wall when the revolution comes."
--- AJS, quoting an uncertain source.

Reply via email to