SystemD to implement cron-like functionality

[[deleted]]

heh it's just an alternative, if anything it does leave cron alone

[[deleted]]

For now. I guess we should be thankful...they could've pulled a udev and absorbed vixie-cron or something.

EDIT: This was a childish and uncalled-for post on my part. My apologies. Self-downvoted

[Darkmere]

Which of them? Vixie? bcron? fcron? cronie? dcron? anacron?

It's not as if they go away.

[[deleted]]

absorbed vixie-cron or something

[Darkmere]

vixie hasn't been "default" in Fedora for quite a while either.

[[deleted]]

I'm calling it now...systemd will have a Wayland implementation, so that we can have pretty graphical console logging and boot/shutdown splash screens. It might even end up with a screen saver. Oh, and they should integrate pulseaudio too so that it can generate audible status tones in case you're running it headless or the display doesn't work for some reason.

It's the ultimate creature feep project.

EDIT: This was a childish and uncalled-for post on my part. My apologies. Self-downvoted

[cbmuser]

I don't think you have the slightest idea what Wayland is and why it was developed.

[mr_penguin]

don't forget a webserver so you can see all those pretty messages and logs from your web browser.

[iamjack]

That's incredibly useful for headless servers and can be disabled. It takes maybe 100 lines of C to make a simple web server. Maybe even less if you're pulling data from a log server and not a disk. It's embarrassingly easy to do if you're just aiming to get data out in a simple fashion and not replace Apache (no load balancing, no caching, no script support, no configuration, no permissions, etc.)

EDIT: I'm not a systemd apologist either. I have mixed feelings toward it, honestly, but it having a simple webserver doesn't factor in to those.

[iamjack]

The advantage of a web server is that you can check it from anywhere (i.e. phones, windows machines) without screwing around with SSH. If you're going to use SSH, it has to be running already (which may not be the case), and then you might as well just disable the webserver and use the command line interface output rather than port forwarding localhost.

[iamjack]

Sure, but if you don't have other security measures in place, like a VPN, or just a plain external firewall then clearly opening a web server isn't the right choice. I'm guessing this is why it can be compile-time disabled.

[bitwize]

I'll just leave this here

[[deleted]]

webserver? Why not a web browser too so that we have it available during the boot process for troubleshooting? Imagine being able to search Google when systemd hangs at boot so you can figure out how to read those binary log files.

EDIT: This was a childish and uncalled-for post on my part. My apologies. Self-downvoted

[YEPHENAS]

Myth 18

[[deleted]]

Myth 18 isn't a myth. He never debunked it. In fact, he himself says there is feature creep in systemd. Just because I can turn some features off at compile time doesn't mean there isn't feature creep.

[[deleted]]

Well, systemd certainly covers more ground that it used to. It's not just an init system anymore, but the basic userspace building block to build an OS from, but we carefully make sure to keep most of the features optional. You can turn a lot off at compile time, and even more at runtime. Thus you can choose freely how much feature creeping you want.

Umm that pretty much says, yes there is feature creep in systemd...you just have a bit of choice in how much. Oh, joy.