13.12.2013 20:08, Peter Stuge пишет:
> Sergey Popov wrote:
> Last time I checked, vixie-cron upstream was died
If vixie-cron upstream is dead as you say
>>>
>>> Define dead?
>>
>> Bugs are not fixed for a very long time, no answers on private
>> e-mails or in maillists.
>
> Define ve
On Sun, Dec 15, 2013 at 2:19 AM, Michael Orlitzky wrote:
> rc-update del vixie-cron default
> /etc/init.d/vixie-cron stop
> emerge -C vixie-cron
> emerge cronie
> rc-update add cronie default
> /etc/init.d/cronie start
I Just did the same, is simple and "drop-in"
--
Gentoo, If it
On 12/23/2013 10:54 PM, Vadim A. Misbakh-Soloviov wrote:
>> rc-update del vixie-cron default
>> /etc/init.d/vixie-cron stop
>> emerge -C vixie-cron
>> emerge cronie
>> rc-update add cronie default
>> /etc/init.d/cronie start
>
> Why /etc/init.d instead of rc-service? :)
>
Uhh
> rc-update del vixie-cron default
> /etc/init.d/vixie-cron stop
> emerge -C vixie-cron
> emerge cronie
> rc-update add cronie default
> /etc/init.d/cronie start
Why /etc/init.d instead of rc-service? :)
--
Best regsrds,
mva
signature.asc
Description: This is a digitally signed mess
Dnia 2013-12-15, o godz. 00:13:09
Peter Stuge napisał(a):
> Markos Chandras wrote:
> > Please do not let Peter render another thread useless.
>
> Isn't it obvious that the discussion about forks is both related to
> cron *and* useful on its own?
No, it's not. We may as well consider systemd a c
On Sunday 15 of December 2013 00:13:09 Peter Stuge wrote:
| Markos Chandras wrote:
| > Please do not let Peter render another thread useless.
|
| Isn't it obvious that the discussion about forks is both related to
| cron *and* useful on its own?
I think there's some misunderstanding (or otherwise
Markos Chandras wrote:
> Please do not let Peter render another thread useless.
Isn't it obvious that the discussion about forks is both related to
cron *and* useful on its own?
It's not really possible to view an entire thread as a single item.
Life is more complicated than that, for good and ba
On 12/11/2013 03:03 PM, Mike Gilbert wrote:
>>
>> Is cronie a drop-in replacement, or do I have to do some thinking when
>> replacing vixie-cron?
>>
>
> It should be a drop-in. The only change to make would be to remove
> vixie-cron and add cronie to the default runlevel.
>
I noticed two small d
Mike Gilbert wrote:
> On Wed, Dec 11, 2013 at 2:25 PM, Michael Orlitzky wrote:
>> On 12/10/2013 09:18 PM, Paul B. Henson wrote:
>>> I'd say go one step further and get rid of vixie-cron completely, is
>>> there anything it does that cronie can't do as well or better?
>> Is cronie a drop-in replace
On 12/13/2013 04:53 PM, Brian Dolbec wrote:
> On Fri, 2013-12-13 at 17:08 +0100, Peter Stuge wrote:
>> Sergey Popov wrote:
>> Last time I checked, vixie-cron upstream was died
>
> If vixie-cron upstream is dead as you say
Define dead?
>>>
>>> Bugs are not fixed for a very long
On Fri, 2013-12-13 at 17:08 +0100, Peter Stuge wrote:
> Sergey Popov wrote:
> > >>> Last time I checked, vixie-cron upstream was died
> > >>
> > >> If vixie-cron upstream is dead as you say
> > >
> > > Define dead?
> >
> > Bugs are not fixed for a very long time, no answers on private
> > e-mails
On Fri, Dec 13, 2013 at 10:08 AM, Peter Stuge wrote:
> Sergey Popov wrote:
> > >>> Last time I checked, vixie-cron upstream was died
> > >>
> > >> If vixie-cron upstream is dead as you say
> > >
> > > Define dead?
> >
> > Bugs are not fixed for a very long time, no answers on private
> > e-mails
Sergey Popov wrote:
> >>> Last time I checked, vixie-cron upstream was died
> >>
> >> If vixie-cron upstream is dead as you say
> >
> > Define dead?
>
> Bugs are not fixed for a very long time, no answers on private
> e-mails or in maillists.
Define very long time?
//Peter
pgpf3lhVFAsOu.pgp
12.12.2013 01:07, Peter Stuge пишет:
> Markos Chandras wrote:
>>> Last time I checked, vixie-cron upstream was died
>>
>> If vixie-cron upstream is dead as you say
>
> Define dead?
>
>
> //Peter
>
Bugs are not fixed for a very long time, no answers on private e-mails
or in maillists.
--
Best
On 12/10/2013 09:55 PM, Pacho Ramos wrote:
https://bugs.gentoo.org/show_bug.cgi?id=197625#c14
This has reminded me that maybe we should switch to cronie from
vixie-cron as default and recommended cron provider in Handbook. Last
time I checked, vixie-cron upstream was died while cronie forked it
Am Wed, 11 Dec 2013 23:42:03 +
schrieb Pavlos Ratis :
> On Tue, Dec 10, 2013 at 8:55 PM, Pacho Ramos wrote:
>
> > https://bugs.gentoo.org/show_bug.cgi?id=197625#c14
> >
> > This has reminded me that maybe we should switch to cronie from
> > vixie-cron as default and recommended cron provider
On Tue, Dec 10, 2013 at 8:55 PM, Pacho Ramos wrote:
> https://bugs.gentoo.org/show_bug.cgi?id=197625#c14
>
> This has reminded me that maybe we should switch to cronie from
> vixie-cron as default and recommended cron provider in Handbook. Last
> time I checked, vixie-cron upstream was died while
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11.12.2013 22:07, Peter Stuge wrote:
>> If vixie-cron upstream is dead as you say
> Define dead?
The latest upstream release is this:
cron_4.1.shar 2004-Jan-23 19:20:23200.7K application/octet-stream
As you can see, it will turn ten soon.
On Wed, Dec 11, 2013 at 1:30 PM, Peter Stuge wrote:
>
>
> I think that nobody who is not intimately familiar with the
> development in both projects can think anything that is actionable.
>
> It's insulting to see how people all over the internet run as fast
> as they possibly can in whatever dire
Markos Chandras wrote:
> > Last time I checked, vixie-cron upstream was died
>
> If vixie-cron upstream is dead as you say
Define dead?
//Peter
On Wed Dec 11 23:30:58 2013 Peter Stuge wrote:
> Pacho Ramos wrote:
> > Last time I checked, vixie-cron upstream was died while cronie
> > forked it fixing some bugs :/
> >
> > What do you think?
>
> I think that nobody who is not intimately familiar with the
> development in both projects can t
On 12/10/2013 08:55 PM, Pacho Ramos wrote:
> https://bugs.gentoo.org/show_bug.cgi?id=197625#c14
>
> This has reminded me that maybe we should switch to cronie from
> vixie-cron as default and recommended cron provider in Handbook. Last
> time I checked, vixie-cron upstream was died while cronie fo
On Wed, Dec 11, 2013 at 2:25 PM, Michael Orlitzky wrote:
> On 12/10/2013 09:18 PM, Paul B. Henson wrote:
>>
>> I'd say go one step further and get rid of vixie-cron completely, is
>> there anything it does that cronie can't do as well or better?
>
> Is cronie a drop-in replacement, or do I have to
Pacho Ramos wrote:
> Last time I checked, vixie-cron upstream was died while cronie
> forked it fixing some bugs :/
>
> What do you think?
I think that nobody who is not intimately familiar with the
development in both projects can think anything that is actionable.
It's insulting to see how peo
On 12/10/2013 09:18 PM, Paul B. Henson wrote:
>
> I'd say go one step further and get rid of vixie-cron completely, is
> there anything it does that cronie can't do as well or better?
Is cronie a drop-in replacement, or do I have to do some thinking when
replacing vixie-cron?
On Tue, Dec 10, 2013 at 09:55:05PM +0100, Pacho Ramos wrote:
> https://bugs.gentoo.org/show_bug.cgi?id=197625#c14
>
> This has reminded me that maybe we should switch to cronie from
> vixie-cron as default and recommended cron provider in Handbook. Last
> time I checked, vixie-cron upstream was di
> From: Pacho Ramos [mailto:pa...@gentoo.org]
> Sent: Tuesday, December 10, 2013 12:55 PM
>
> This has reminded me that maybe we should switch to cronie from
> vixie-cron as default and recommended cron provider in Handbook. Last
> time I checked, vixie-cron upstream was died while cronie forked it
I'm a nobody, but +1 from me.
On 10 December 2013 16:33, Lars Wendler wrote:
> Am Tue, 10 Dec 2013 21:55:05 +0100
> schrieb Pacho Ramos :
>
> > https://bugs.gentoo.org/show_bug.cgi?id=197625#c14
> >
> > This has reminded me that maybe we should switch to cronie from
> > vixie-cron as default an
Am Tue, 10 Dec 2013 21:55:05 +0100
schrieb Pacho Ramos :
> https://bugs.gentoo.org/show_bug.cgi?id=197625#c14
>
> This has reminded me that maybe we should switch to cronie from
> vixie-cron as default and recommended cron provider in Handbook. Last
> time I checked, vixie-cron upstream was died
https://bugs.gentoo.org/show_bug.cgi?id=197625#c14
This has reminded me that maybe we should switch to cronie from
vixie-cron as default and recommended cron provider in Handbook. Last
time I checked, vixie-cron upstream was died while cronie forked it
fixing some bugs :/
What do you think?
30 matches
Mail list logo
