On Sb, 08 mai 21, 10:12:59, l0f...@tuta.io wrote:
> Hi,
>
> 5 mai 2021, 04:48 de deb...@lionunicorn.co.uk:
>
> > After all, it's easy to override it with
> >
> > # ln -s /dev/null /etc/systemd/system/btrbk.service
> >
> You may need the `-f` (force) switch if btrbk.service file already exists.
Hi,
5 mai 2021, 04:48 de deb...@lionunicorn.co.uk:
> After all, it's easy to override it with
>
> # ln -s /dev/null /etc/systemd/system/btrbk.service
>
You may need the `-f` (force) switch if btrbk.service file already exists.
Best regards,
l0f4r0
On Tue 04 May 2021 at 22:20:14 (+0300), Andrei POPESCU wrote:
> On Ma, 04 mai 21, 19:50:27, Mart van de Wege wrote:
> > David Wright writes:
> > > On Tue 04 May 2021 at 17:06:50 (+0200), Mart van de Wege wrote:
> > >>
> > >> Surely packaging a system timer file like that should not be done? It
>
On Ma, 04 mai 21, 19:50:27, Mart van de Wege wrote:
> David Wright writes:
>
> > On Tue 04 May 2021 at 17:06:50 (+0200), Mart van de Wege wrote:
> >>
> >> 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
David Wright writes:
> On Tue 04 May 2021 at 17:06:50 (+0200), Mart van de Wege wrote:
>> Sven Hartge writes:
>> > Mart van de Wege 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?
>> >
>> >
On Tue 04 May 2021 at 17:06:50 (+0200), Mart van de Wege wrote:
> Sven Hartge writes:
> > Mart van de Wege 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,
Sven Hartge writes:
> Mart van de Wege 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
Mart van de Wege 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.
Mart van de Wege writes:
> Stefan Monnier writes:
>
>> Mart van de Wege [2021-05-03 20:11:25] wrote:
>>> Stefan Monnier writes:
> root@galahad:~# grep btrbk /etc/ -rl
Have you `grep`d in `/var/` as well?
[ E.g. `/var/spool/crontabs` ]
>>> Yep, nothing there, aside from
Stefan Monnier writes:
> Mart van de Wege [2021-05-03 20:11:25] wrote:
>> Stefan Monnier writes:
root@galahad:~# grep btrbk /etc/ -rl
>>>
>>> Have you `grep`d in `/var/` as well?
>>> [ E.g. `/var/spool/crontabs` ]
>>>
>> Yep, nothing there, aside from the usual suspects (apt & dpkg files).
On Mon, May 03, 2021 at 02:37:36PM -0400, Stefan Monnier wrote:
> Mart van de Wege [2021-05-03 20:11:25] wrote:
[...]
> > Not that I can see. I am going to see what patching btrbk to log PPID
> > shows up tonight.
>
> My usual "trick" is to log a full `ps --forest -ef`.
> [ Instead of patching,
Mart van de Wege [2021-05-03 20:11:25] wrote:
> Stefan Monnier writes:
>>> root@galahad:~# grep btrbk /etc/ -rl
>>
>> Have you `grep`d in `/var/` as well?
>> [ E.g. `/var/spool/crontabs` ]
>>
> Yep, nothing there, aside from the usual suspects (apt & dpkg files).
>
>>> And yet I find this in
Stefan Monnier writes:
>> root@galahad:~# grep btrbk /etc/ -rl
>
> Have you `grep`d in `/var/` as well?
> [ E.g. `/var/spool/crontabs` ]
>
Yep, nothing there, aside from the usual suspects (apt & dpkg files).
>> And yet I find this in /var/log/btrbk.log:
>>
>> 2017-03-12T20:16:28+0100 startup
> root@galahad:~# grep btrbk /etc/ -rl
Have you `grep`d in `/var/` as well?
[ E.g. `/var/spool/crontabs` ]
> And yet I find this in /var/log/btrbk.log:
>
> 2017-03-12T20:16:28+0100 startup v0.24.0 - - - - # btrbk command line client,
> version 0.24.0
Any other mention of activity around that
David Wright writes:
>
> Just guessing. You set the cron job to initiate a backup at 04:00.
> Perhaps there's something configured in your /etc/btrbk/btrbk.conf
> that says check for retention by day/week/month/year rather than
> 04:00/day/week/month/year. The former check has to made at
On Mon 03 May 2021 at 09:07:26 (+0200), Mart van de Wege wrote:
> I have the following configured to back up my laptop to my file server:
>
> root@galahad:~# cat /etc/cron.d/backup
> MAILTO=m...@vdwege.eu
> #00 04 * * * root /usr/sbin/btrbk --verbose --format=long run
>
> Note: it is currently
writes:
> Now I do :)
>
> Well, no clue. But it's a script, so you could just insert some
> debugging stuff (like, for example, reporting its parent PID
> when it's started again)? So you might catch the ghosts parent?
>
> Cheers
> - t
>
Neat idea. btrbk is pure Perl, in which I happened to be
On Mon, May 03, 2021 at 09:54:24AM +0200, Mart van de Wege wrote:
> writes:
>
> > On Mon, May 03, 2021 at 09:07:26AM +0200, Mart van de Wege wrote:
> >> I have the following configured to back up my laptop to my file server:
> >>
> >> root@galahad:~# cat /etc/cron.d/backup
> >>
writes:
> On Mon, May 03, 2021 at 09:07:26AM +0200, Mart van de Wege wrote:
>> I have the following configured to back up my laptop to my file server:
>>
>> root@galahad:~# cat /etc/cron.d/backup
>> MAILTO=m...@vdwege.eu
>> #00 04 * * * root /usr/sbin/btrbk --verbose --format=long run
>>
>>
On Mon, May 03, 2021 at 09:07:26AM +0200, Mart van de Wege wrote:
> I have the following configured to back up my laptop to my file server:
>
> root@galahad:~# cat /etc/cron.d/backup
> MAILTO=m...@vdwege.eu
> #00 04 * * * root /usr/sbin/btrbk --verbose --format=long run
>
> Note: it is
Mart van de Wege writes:
> And yet I find this in /var/log/btrbk.log:
>
> 2017-03-12T20:16:28+0100 startup v0.24.0 - - - - # btrbk command line client,
> version 0.24.0
>
Wrong logline copy/pasted, it should be this one:
2021-05-03T00:00:03+0200 startup v0.27.1 - - - # btrbk command line
21 matches
Mail list logo
