On Fri, Mar 08, 2019 at 07:27:19PM -0500, Michael Stone wrote:
> On Sat, Mar 09, 2019 at 12:02:05AM +0200, Adrian Bunk wrote:
> > On Fri, Mar 08, 2019 at 02:38:07PM -0500, Michael Stone wrote:
> > > On Fri, Mar 08, 2019 at 08:01:35PM +0100, Christian Kastner wrote:
> > > > I intended to post a tran
On Sat, Mar 09, 2019 at 12:02:05AM +0200, Adrian Bunk wrote:
On Fri, Mar 08, 2019 at 02:38:07PM -0500, Michael Stone wrote:
On Fri, Mar 08, 2019 at 08:01:35PM +0100, Christian Kastner wrote:
> I intended to post a transition proposal here soon, but it's not ready
> yet... but long story short: I
On Fri, Mar 08, 2019 at 02:38:07PM -0500, Michael Stone wrote:
> On Fri, Mar 08, 2019 at 08:01:35PM +0100, Christian Kastner wrote:
> > I intended to post a transition proposal here soon, but it's not ready
> > yet... but long story short: I believe we would be far better off moving
> > to cronie t
On 2019-03-08 20:12 +0100, Tollef Fog Heen wrote:
> ]] Adrian Bunk
>
>> Something will break (like in the mlocate case), and people might only
>> start noticing when they are doing fresh installs of buster after the
>> release.
>
> Which mlocate case is this?
Bug #882993, updatedb.mlocate will
On 08.03.19 20:38, Michael Stone wrote:
> On Fri, Mar 08, 2019 at 08:01:35PM +0100, Christian Kastner wrote:
>> I intended to post a transition proposal here soon, but it's not ready
>> yet... but long story short: I believe we would be far better off moving
>> to cronie than maintaining our old fo
On Fri, Mar 08, 2019 at 08:01:35PM +0100, Christian Kastner wrote:
I intended to post a transition proposal here soon, but it's not ready
yet... but long story short: I believe we would be far better off moving
to cronie than maintaining our old fork.
One question worth asking is which distribu
(Speaking as one of the cron maintainers)
On 08.03.19 19:28, Adam Borowski wrote:
> On Fri, Mar 08, 2019 at 10:22:12AM -0800, Russ Allbery wrote:
>> cron is effectively maintained by the distributions anyway; there
>> hasn't been an official upstream release in more than twenty years.
>> This seem
]] Adrian Bunk
> Something will break (like in the mlocate case), and people might only
> start noticing when they are doing fresh installs of buster after the
> release.
Which mlocate case is this?
--
Tollef Fog Heen, mlocate maintainer
UNIX is user friendly, it's just picky about who its f
On Fri, Mar 08, 2019 at 10:22:12AM -0800, Russ Allbery wrote:
> Simon McVittie writes:
>
> > anacron/cron don't have a built-in way to skip particular cron jobs
> > other than open-coding it in the cron job itself.
>
> Maybe we should just fix this? cron is effectively maintained by the
> distr
On Fri, Mar 08, 2019 at 07:28:11PM +0100, Adam Borowski wrote:
> There's a problem with extending the syntax: we have not one but five cron
> implementations in the distributions, and all would need to be in sync,
Not necessarily. Being in sync isn't required for init scripts.
--
WBR, wRAR
sign
On Fri, Mar 08, 2019 at 10:22:12AM -0800, Russ Allbery wrote:
> Simon McVittie writes:
>
> > anacron/cron don't have a built-in way to skip particular cron jobs
> > other than open-coding it in the cron job itself.
>
> Maybe we should just fix this? cron is effectively maintained by the
> distr
Simon McVittie writes:
> anacron/cron don't have a built-in way to skip particular cron jobs
> other than open-coding it in the cron job itself.
Maybe we should just fix this? cron is effectively maintained by the
distributions anyway; there hasn't been an official upstream release in
more than
On Fri, 8 Mar 2019 at 15:15, Daniel Reichelt wrote:
>
> > And surely we support other, strange and not so strange, choices,
> > sometimes more and sometimes less, but yawn.
>
> And yet Debian claims to support - pardon - offer init systems other
> than systemd for usage.
>
>
> Either: make a clean
On Fri, 8 Mar 2019 at 14:48, Holger Levsen wrote:
>
> On Fri, Mar 08, 2019 at 01:46:59PM +, Daniel Reichelt wrote:
> > > Shouldn't that be the other way around? Having .timer but not a cronjob
> > > is
> > > a nasty bug, having a cronjob but not .timer is fine (at least unless you
> > > have
> And surely we support other, strange and not so strange, choices,
> sometimes more and sometimes less, but yawn.
And yet Debian claims to support - pardon - offer init systems other
than systemd for usage.
Either: make a clean cut, kick out everything that has been obsoleted™
by pötterd, there
On Fri, Mar 08, 2019 at 01:46:59PM +, Daniel Reichelt wrote:
> > Shouldn't that be the other way around? Having .timer but not a cronjob is
> > a nasty bug, having a cronjob but not .timer is fine (at least unless you
> > have no cron implementation at all).
> +1!
/me yawns. init systemd disc
> Shouldn't that be the other way around? Having .timer but not a cronjob is
> a nasty bug, having a cronjob but not .timer is fine (at least unless you
> have no cron implementation at all).
+1!
signature.asc
Description: OpenPGP digital signature
On Fri, Mar 08, 2019 at 02:16:13PM +0100, Laurent Bigonville wrote:
> Simon McVittie wrote:
>
> > In a more opinionated distribution the solution would have been "require
> > systemd, rely on systemd timers, delete cron jobs, move on", but Debian
> > still supports non-systemd init as a non-defaul
Simon McVittie wrote:
In a more opinionated distribution the solution would have been "require
systemd, rely on systemd timers, delete cron jobs, move on", but Debian
still supports non-systemd init as a non-default installation, and
anacron/cron don't have a built-in way to skip particular cron
> On Fri, 08 Mar 2019 at 10:24:28 +0200, Adrian Bunk wrote:
> > The output of "ls /etc/cron.daily" is not empty for me.
>
> That doesn't *necessarily* mean you need anacron, or even cron. Many
> cron jobs now have a corresponding systemd timer; if you are running
> systemd, the cron job starts, de
On Fri, Mar 08, 2019 at 11:22:36AM +0100, Paride Legovini wrote:
> Hello Adrian,
Hi Paride,
> Adrian Bunk wrote on 08/03/2019:
> > On Thu, Mar 07, 2019 at 10:11:41PM +0100, Paride Legovini wrote:
>...
> >> Having a useless service running is itself a downside; I second the
> >> removal.
> >
> >
On Fri, Mar 08, 2019 at 09:47:34AM +, Simon McVittie wrote:
> On Thu, 07 Mar 2019 at 17:07:18 -0400, David Bremner wrote:
> > Holger Wansing writes:
> > > Are there still many packages, that don't rely on systemd timer units?
> >
> > Presumably packages that work without systemd, but still ne
On Thu, 7 Mar 2019 15:06:16 -0500, Michael Stone
wrote:
>On Thu, Mar 07, 2019 at 09:02:23PM +0100, Holger Wansing wrote:
>>> I'm actually wondering if this is a good idea..
>>>
>>> There are lot of other packages installing cronjobs and people, I would
>>> assume, expect that they will run.
>>>
>>
Hello Adrian,
Adrian Bunk wrote on 08/03/2019:
> On Thu, Mar 07, 2019 at 10:11:41PM +0100, Paride Legovini wrote:
>> Michael Stone wrote on 07/03/2019:
>>> On Thu, Mar 07, 2019 at 09:02:23PM +0100, Holger Wansing wrote:
> I'm actually wondering if this is a good idea..
>
> There are lo
On Thu, 07 Mar 2019 at 17:07:18 -0400, David Bremner wrote:
> Holger Wansing writes:
> > Are there still many packages, that don't rely on systemd timer units?
>
> Presumably packages that work without systemd, but still need to
> periodic activity?
Default installations of Debian boot with syst
On Thu, Mar 07, 2019 at 10:11:41PM +0100, Paride Legovini wrote:
> Michael Stone wrote on 07/03/2019:
> > On Thu, Mar 07, 2019 at 09:02:23PM +0100, Holger Wansing wrote:
> >>> I'm actually wondering if this is a good idea..
> >>>
> >>> There are lot of other packages installing cronjobs and people,
Paride Legovini wrote:
Having a useless service running is itself a downside; I second the
removal. I'll also mention that anacron has been orphaned almost one
year ago.
anacron is AFAICS not running as a service (at least not all the time),
it is started by cron (or systemd) every hours and ex
Holger Wansing writes:
>
> Any thoughts on this?
>
> Is there still a broad necessity for anacron?
> Are there still many packages, that don't rely on systemd timer units?
>
Presumably packages that work without systemd, but still need to
periodic activity?
d
Michael Stone wrote on 07/03/2019:
> On Thu, Mar 07, 2019 at 09:02:23PM +0100, Holger Wansing wrote:
>>> I'm actually wondering if this is a good idea..
>>>
>>> There are lot of other packages installing cronjobs and people, I would
>>> assume, expect that they will run.
cronjobs run even without
On Thu, Mar 07, 2019 at 09:02:23PM +0100, Holger Wansing wrote:
I'm actually wondering if this is a good idea..
There are lot of other packages installing cronjobs and people, I would
assume, expect that they will run.
I would personally revert his patch as long as all the cronjobs have not
a c
[ Forwarding this to -devel ]
Hi,
Laurent Bigonville wrote:
> On Mon, 03 Dec 2018 09:44:05 +0100 Michael Biebl wrote:
>
> Hello,
>
> >
> > anacron was added to the desktop-task a long time ago.
> > The changelog doesn't mention why it was added, but I assume it was to
> > support systems
31 matches
Mail list logo
