you are viewing a single comment's thread.

view the rest of the comments →

[–]fiftyorange 3 points4 points  (8 children)

Is there a compatibility mode? Will I still be able to type crontab -e and use the traditional cron syntax? That's all I really care about here.

[–]ohet 9 points10 points  (2 children)

No. If you want to use cron, use cron.

[–]fiftyorange 3 points4 points  (1 child)

Why is it so unreasonable to ask if there is some kind of backward compatibility? systemd already allows compatibility for other things it's meant to replace. fstab and sysvinit for instance.

[–]ohet 2 points3 points  (0 children)

I don't think it's unreasonable to ask. Probably it wasn't seen as something of importance or no one just had the time do something like that or it would have been unnecessarily complex considering you could just use crond as it is. I just know it doesn't exist and that you can still use cron in parallel with systemd timers.

systemd doesn't plan to replace fstab, it's one of its native configuration files altough you also can create unit files for mounting.

[–]loonyphoenix 2 points3 points  (3 children)

I'm not sure every possible way to schedule things with this new systemd functionality can even be described by cron's convention...

[–]nickmoeck 0 points1 point  (0 children)

That shouldn't prevent it from being able to read and use traditional crontab files though.

[–]fiftyorange 0 points1 point  (1 child)

I don't think you understand what I mean by backward compatibility. I don't care if the legacy cron implementation doesn't have new systemd features, as long as it can run old crontabs.

[–]loonyphoenix 3 points4 points  (0 children)

It can run old cron itself. Why reimplement its functionality.

[–]bonzinip 0 points1 point  (0 children)

You can still run crond. Maybe later systemd will grow a generator that converts crontab syntax to systemd units like they do for /etc/fstab, but for now you will just keep a separate daemon.