Linux

48366 readers

1158 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

328

Systemd: Hidden Gems for a Better Linux (tadeubento.com)

submitted 1 year ago by TCB13@lemmy.world to c/linux@lemmy.ml

90 comments fedilink hide all child comments

After a few conversations with people on Lemmy and other places it became clear to me that most aren't aware of what it can do and how much more robust it is compared to the usual "jankiness" we're used to.

In this article I highlight less known features and give out a few practice examples on how to leverage Systemd to remove tons of redundant packages and processes.

And yes, Systemd does containers. :)

you are viewing a single comment's thread
view the rest of the comments

[–] nomadjoanne@lemmy.world 1 points 1 year ago (1 children)

Very cool. I had no idea systemd sort of has a cron replacement. While in I don't think I'll switch from cron in the immediate future, it's really good to know.

[–] TCB13@lemmy.world 10 points 1 year ago (2 children)

Systemd timers are way, way better than cron. Because can audit them, view when they last run, next expected run, can be set to persist with reboot or not, aggregate logs under journalctl, can do amazing things such as "x minutes after boot", can be configured not to run again until the last run is complete etc... https://opensource.com/article/20/7/systemd-timers

[–] nomadjoanne@lemmy.world 2 points 1 year ago* (last edited 1 year ago) (1 children)

Fully agreed. But I know how to use cron, I have a life to live, and this switch is way down the priority list.

But it is something I'd like to find the time to do at some point.

[–] TCB13@lemmy.world 2 points 1 year ago

Well if it makes you more comfortable let me tell you that the format of OnCalendar is the same, or very close. I bet that just by looking at the following you know what is does!

[Unit]
Description=Logs some system statistics to the systemd journal
Requires=myMonitor.service

[Timer]
Unit=myMonitor.service
OnCalendar=*-*-* *:*:00

[Install]
WantedBy=timers.target

[–] michaelrose@lemmy.ml 1 points 1 year ago

You can do most of that with cron as well https://man.archlinux.org/man/fcrontab.5.en. If you want details about successful runs I think you would have to ensure you always logged.