Hi Peter,
I've just uploaded anacron 2.3-24 to DELAYED/3 with the following changes:
> anacron (2.3-24) unstable; urgency=medium
>
> * Team upload.
> * Reference anacron and anacrontab man page in anacron.service
> * Use native systemd timer unit to trigger anacron periodically.
>
Of course, my proposed patches would requires that the machine is
turned on at xx:00 at least once a day.
Although that patch is much better than the current behavior, I don't think
that the solution is general enough.
It's perfectly legitimate to use a device only for some minutes every time
tag 744753 + help
thanks
Hello,
Could somebody take care of this bug? I don't have the time for this
ATM.
Cheers,
Laurent Bigonville
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I don't know much about systemd, so I can't be of much help with this.
If anyone wants to take responsibility for a solution, please go ahead.
(Also consider addressing #771393 at the same time.)
An alternative would be to remove systemd support from the package for
the release and rely on the
A much smaller change would just to add the following file in the
cron.hourly directory (not tested):
8
#!/bin/sh
/usr/sbin/invoke-rc.d anacron start /dev/null
8
Of course, my proposed patches would requires that the machine is
turned on at xx:00 at least once a day. And
tag 744753 + patch
thanks
Le Wed, 29 Oct 2014 10:50:27 +0100,
Laurent Bigonville bi...@debian.org a écrit :
Michael was proposing another solution. Instead of waking anacron at
boot and just after sleep, we could run it every hour. So it would be
quite unlikely that anacron is not run at
Le Sun, 16 Nov 2014 20:42:57 +0100,
Laurent Bigonville bi...@debian.org a écrit :
[...]
Tell me what do you think about this.
A much smaller change would just to add the following file in the
cron.hourly directory (not tested):
8
#!/bin/sh
/usr/sbin/invoke-rc.d anacron start
Le Tue, 28 Oct 2014 13:24:53 +0100,
Laurent Bigonville bi...@debian.org a écrit :
severity 744753 serious
thanks
Hello,
IMHO this bug should be serious as anacron is more or less useless
without this.
Do we have a consensus on a solution here?
Michael was proposing another solution.
severity 744753 serious
thanks
Hello,
IMHO this bug should be serious as anacron is more or less useless
without this.
Do we have a consensus on a solution here?
Cheers,
Laurent Bigonville
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe.
On Fri, 27.06.14 20:45, Michael Biebl (bi...@debian.org) wrote:
Am 27.06.2014 20:10, schrieb Lennart Poettering:
Well, I know that much. But a service which needs to be restarted on
cases like this sounds wrong. Thats a hack really. The service should
just watch time changes and react
On Wed, 04.06.14 11:48, Sam Morris (s...@robots.org.uk) wrote:
On Tue, Jun 03, 2014 at 08:25:25PM +0200, Lennart Poettering wrote:
On Tue, 03.06.14 05:43, Michael Biebl (bi...@debian.org) wrote:
Lennart, do you have better solution for such services which need to be
restarted on
Am 27.06.2014 20:10, schrieb Lennart Poettering:
Well, I know that much. But a service which needs to be restarted on
cases like this sounds wrong. Thats a hack really. The service should
just watch time changes and react correctly to that. i.e. use
TFD_TIMER_CANCEL_ON_SET. THis will report
On Tue, Jun 03, 2014 at 08:25:25PM +0200, Lennart Poettering wrote:
On Tue, 03.06.14 05:43, Michael Biebl (bi...@debian.org) wrote:
Lennart, do you have better solution for such services which need to be
restarted on suspend/resume?
Why would a service need something like this? This
On Tue, 03.06.14 05:43, Michael Biebl (bi...@debian.org) wrote:
Lennart, do you have better solution for such services which need to be
restarted on suspend/resume?
Why would a service need something like this? This sounds systematically
flawed... I'd really try to focus on that and fix the
On Mon, Apr 14, 2014 at 11:42:52AM +, Sam Morris wrote:
Package: anacron
Version: 2.3-19
Severity: normal
Tags: patch
Anacron currently ships a pm-utils hook script that starts the service
when the system is resumed. pm-utils hooks are not executed when the
system resumes, having been
Am 03.06.2014 05:43, schrieb Michael Biebl:
I would simplify the first solution a bit though, and simply run a
try-restart on post, i.e. something like this
#!/bin/bash
[ $1 = post ] systemctl try-restart anacron.service
Actually, better make that restart instead of try-restart, since
Am 03.06.2014 05:56, schrieb Michael Biebl:
Am 03.06.2014 05:43, schrieb Michael Biebl:
I would simplify the first solution a bit though, and simply run a
try-restart on post, i.e. something like this
#!/bin/bash
[ $1 = post ] systemctl try-restart anacron.service
Actually, better make
Package: anacron
Version: 2.3-19
Severity: normal
Tags: patch
Anacron currently ships a pm-utils hook script that starts the service
when the system is resumed. pm-utils hooks are not executed when the
system resumes, having been suspended by systemd.
Systemd provides a directory,
18 matches
Mail list logo
