Usually such things have a simple explanation. systemd does a lot with time and date, for example scheduling tasks. It’s quite obvious that it has this capabilities, when you think about it.
Usually such things have a simple explanation. systemd does a lot with time and date, for example scheduling tasks. It’s quite obvious that it has this capabilities, when you think about it.
But that has been a complaint for 10 years and it’s only gotten worse
I wouldn’t mind systemd if it weren’t for the fact that it was to be a startup system that promised to make everything easier and faster to startup yet managing systemd is a drag at best, and of it did one thing it’s making my systems boot up like mud
Is it? It was always super easy to get anything done and with systems it suddenly got factors more complicated. Port assignment was super easy to do, note the past tense. It now requires systemd and instead of a 15 second config file change and service restart I now need to create and delete files, restart multiple services, God knows what in systems.
Simply put: why? If you make an alternative solution AT LEAST it shouldn’t become way more over complicated to get basic tasks done
I definitely think so. Init was a mess of bash scripts and concurrency and whatnot was a problem. Making a script to start a service was very dependent on the distro, their specific decisions and whatnot. Systemd services and timers make things very easy and they have great tools to manage those. And now it’s basically the same on every distro.
Aight, didn’t know that. I cannot yet imagine any scheduled task that would require anything more advanced than cron (or a similar standalone syntax), but I’ll just trust you with that one.
Usually such things have a simple explanation. systemd does a lot with time and date, for example scheduling tasks. It’s quite obvious that it has this capabilities, when you think about it.
Usually such things have a simple explanation. systemd does a lot
with time and date, for example scheduling tasks. It’s quite obvious that it has this capabilities, when you think about it.FTFY
Too much
But that has been a complaint for 10 years and it’s only gotten worse
I wouldn’t mind systemd if it weren’t for the fact that it was to be a startup system that promised to make everything easier and faster to startup yet managing systemd is a drag at best, and of it did one thing it’s making my systems boot up like mud
I feel like the glued together collection of scripts was way worse to manage than systemd.
Is it? It was always super easy to get anything done and with systems it suddenly got factors more complicated. Port assignment was super easy to do, note the past tense. It now requires systemd and instead of a 15 second config file change and service restart I now need to create and delete files, restart multiple services, God knows what in systems.
Simply put: why? If you make an alternative solution AT LEAST it shouldn’t become way more over complicated to get basic tasks done
I definitely think so. Init was a mess of bash scripts and concurrency and whatnot was a problem. Making a script to start a service was very dependent on the distro, their specific decisions and whatnot. Systemd services and timers make things very easy and they have great tools to manage those. And now it’s basically the same on every distro.
Not that that’s bad when it’s stuff like this
Yes it is.
How is this functionality bad?
I never typed this command so it must be bloat that’s eating my 1tb SSD /s
I thought the same, but didn’t we already have things like chron syntax for this? Systemd didn’t have to build its own library.
Systemd’s method is more powerful than Cron syntax.
Aight, didn’t know that. I cannot yet imagine any scheduled task that would require anything more advanced than cron (or a similar standalone syntax), but I’ll just trust you with that one.
Can you tell Cron to catch up on the things that should’ve happened but didn’t because the system was off?
I think fcron and anacron can do that