> Is this the real output from systemd-cron? Then it should be fixed:
Nope, it is not.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! SF
On 21 Mar 2016 09:23, "Alexandre Detiste"
wrote:
>
> 2016-03-21 12:54 GMT+01:00 Felipe Sateler :
> >
> > > [Service]
> > > Type=oneshot
> > > IgnoreSIGPIPE=false
> > > ExecStart=foo
> >
> > Is this the real output from systemd-cron?
>
>
> No
>
> >
2016-03-21 12:54 GMT+01:00 Felipe Sateler :
>
> > [Service]
> > Type=oneshot
> > IgnoreSIGPIPE=false
> > ExecStart=foo
>
> Is this the real output from systemd-cron?
No
>
> Then it should be fixed:
>
> 1. Exec* need their first argument to be a full path.
> 2. Exec* are not
> It's hard to reproduce, some works some don't;
True, the same entry might works sometimes, and sometimes niot.
> Hum, it can replace cron, but only on explicit user request.
> All the cron job consumers depends on "cron | cron-daemon"
> and will always pull vixie cron first.
Right, it's the
> > > This fix is not even list in upstream v230 changelog
> > > not really serious.
> No wonder, as there is no v230 release yet there also is no NEWS for
> it yet :-)
I guess that explains it :)
> Yes, I do plan to do an upload this week.
Great, thanks Martin.
Michael
--
Michael Meskes
On 20 March 2016 at 08:44, Michael Meskes wrote:
> On Sat, Mar 19, 2016 at 09:29:21PM +0100, Alexandre Detiste wrote:
>> Have a look at the generated files under /run/systemd/generator/cron-*.timer
>> + cron-*.service
>> to have a proper comparaison basis.
>
> Here we go.
>
>
Michael Meskes [2016-03-21 11:59 +0100]:
> > This fix is not even list in upstream v230 changelog
> > not really serious.
No wonder, as there is no v230 release yet there also is no NEWS for
it yet :-)
> Anyway, with systemd-cron replacing cron it seems to be paramount to me
> that we get a
2016-03-21 11:59 GMT+01:00 Michael Meskes :
> > > > > It may be only serious, but it definitely is not fit for a
> > > > > release.
> > > > Then systemd 229 is not fit for release.
> > > Indeed you're right imo.
> > This fix is not even list in upstream v230 changelog
> > not
> > > > It may be only serious, but it definitely is not fit for a
> > > > release.
> > > Then systemd 229 is not fit for release.
> > Indeed you're right imo.
> This fix is not even list in upstream v230 changelog
> not really serious.
This surprised me. Doesn't this bug mean that *all* timers
Le dimanche 20 mars 2016, 20:02:37 Michael Meskes a écrit :
> > And as systemd-cron is the only user of timers in Debian;
> > you're the first to notice; thanks !
>
> Surprising, isn't it? Anyway, thanks for debugging.
fstrim did tried to ship a .timer but got immediatly struck down;
I did filed
> And as systemd-cron is the only users of timers in Debian;
> you're the first to notice; thanks !
Surprising, isn't it? Anyway, thanks for debugging.
> There's well an upload pending (need a sponsor)
> to allow non-root to use crontab.
I can do that.
> No, it's broken here to since update to
control: reassign -1 systemd
It seems like systemd v229 broke timers:
https://github.com/systemd/systemd/issues/2682
https://archlinuxarm.org/forum/viewtopic.php?f=57=9892
And as systemd-cron is the only users of timers in Debian;
you're the first to notice; thanks !
Le dimanche 20 mars 2016,
On Sat, Mar 19, 2016 at 09:29:21PM +0100, Alexandre Detiste wrote:
> Have a look at the generated files under /run/systemd/generator/cron-*.timer
> + cron-*.service
> to have a proper comparaison basis.
Here we go.
timer:
[Unit]
Description=[Timer] "14,44 * * * * foo"
control: severity -1 important
> Severity: grave
>
> I just installed systemd-cron to try it out and found that it only partly
> translated my crontabs. For instance my crontab says:
>
> 26 * * * * foo
> 14,44 * * * * bar
>
> However at 21:10 I got this:
>
> michael@feivel:~$ systemctl
On Sat, Mar 19, 2016 at 09:15:00PM +0100, Michael Meskes wrote:
> Also I found that changing a crontab to have something executed in a few
> minutes always gives me a timer in 24 hours.
To make matters worse, the system just (21:22) decided to remove the timer for
21:44 and replace it with one
Package: systemd-cron
Version: 1.5.3-1
Severity: grave
I just installed systemd-cron to try it out and found that it only partly
translated my crontabs. For instance my crontab says:
26 * * * * foo
14,44 * * * * bar
However at 21:10 I got this:
michael@feivel:~$ systemctl list-timers |grep
16 matches
Mail list logo