systemd on Linux 1: Intro and Unit Files

[@tutoriaLinux]

My Linux course for beginners: www.udemy.com/course/hands-on-linux-self-hosted-wordpress-for-linux-beginners/?referralCode=19C0A7DEE2FD53C9C09D Linode Referral Link (you get $100 credit when signing up): www.linode.com/tutorialinux tutorialinux Merch: kzbin.info/door/vA_wgsX6eFAOXI8Rbg_WiQstore My Linux Course Playlist: kzbin.info/aero/PLtK75qxsQaMLZSo7KL-PmiRarU7hrpnwK

[@unixbadger]

I really appreciate how you give some overview and operational examples instead of just diving into the configuration files like most books and videos.

[@tutoriaLinux]

Thank you so much! I often get a lot of "JUST GET TO THE POINT" comments on my videos, but I don't understand how anyone can retain technical information with zero context, so I've kept this format all these years. I guess I'll never be as big as jake paul, oh well :-D

[@DonalTechTips]

Thank you for making this, really interesting and well explained. Looking forward to the rest of the series.

[@sadhucat4476]

This is some of the best explained material I've found anywhere. Every, "but why..." is addressed before moving on to the next step. Subscribed and gonna start checking this channel first when I go researching Linux topics.

[@FailCommando]

Exactly what i was searching for. Thank you so much!

[@Tech-ub8dd]

Thank you for the video, i keep getting confused what systemd unit actually are because i see them all over the place. Love your tutorials!

[@mrdr9534]

Thanks for taking the time and effort of making this video and sharing Your knowledge. This was the best introduction to this subject that I have seen to date, and I have watched quite a number...;), and I will now go on to watch the rest in Your "systemd series" :) Again many thanks. Best regards.

[@_Zabamund_]

This is great thank you, I'm just a Linux and systemd user and while I know python I'm not a Linux sysadmin pro, so this is really helpful.

[@KM-sv4dh]

Your channel is under rated man, I do really enjoy your videos.

[@ArthurDebert]

Thanks!

[@tutoriaLinux]

Thank you so much! Truly generous.

[@YosrDhaoui]

So grateful for finding this video! Thank u so much

[@gregzeng]

This KZbin production business shows the complications of technical communication. This is further detailed by the many comments from all types of viewers to this surviving video. Systemd, as you seem to explain it, is just another automation step that gatherers together a bunch of many small scripts, and both necessary and also optional alternatives. KZbin "journalism" is similar to a large organisation's "Public Office". Your job is to represent the address of interest, only to the uninformed masses, at their selected level of simplicity: infants, children, teenagers, young adults, adults, and retirees. Each target audience really needs specialized attention. It is so hard to be everything to everybody, satisfactorily. All journalism, like all teaching, Chief Officer and parenting roles, is very demanding on our work performances, and the supposed quality of our work output. Systemd tried to be in operating systems, similar to KZbin journalism, Chief Officer and parenting roles. Trying to become all things to all people. Systemd is an evolution to previous "solutions" detailed in this video and its comments from informed viewers. Init,... Etc. Some rebels prefer the older, "simpler" traditional methods. The latest version of Peppermint Linux now offers Debian instead of Ubuntu as a base. It uses Devuan which avoids the newer automation called "systemd", which is the subject of this specific KZbin production. Systemd is a usual further evolutionary development in Linux. Linux was devised to be written in the computer language called "C". After many attempts to upgrade and modify "C", some of the heavyweights in Linux are now slowly trying to move to the "improvement" to C, called "Rust". Systemd, like the introduction of binary computers to machines, is replacing that older method. Older sceptics are resisting this new automation, simplifications and tidy gathering of independent scripts. This is standard evolutionary "progress". Three steps forward, then one or two steps backward.

[@networker9304]

Nice representation for orphaned process. Kudos to creator

[@tornenic]

Very well explained. Thanks a ton!

[@abdelrahmanyasser3879]

This is amazing, thanks for making this.

[@Oswee]

+ systemd-analyze, timer units i found quite important tools in a daily use. I would not put everything under "/etc/systemd/...". You have also "~/.config/systemd/..." for things like gpg-agent etc. Also... it could be quite important to mention about Environment and PassEnvironment to control unit environment. Or "~/.config/environment.d/*". Also "sudo strings /proc//environ" is quite handy at times.

[@tutoriaLinux]

This is a great callout, thank you! I had planned another systemd video about timers but then forgot to do it (oops)! Maybe I'll film it next week. Timers are definitely a core part of the toolbox, and I find myself constantly using Environment/EnvironmentFile as well.

[@portentouslad5051]

Very welcome, thanks for the series.

[@TecraTube]

This video is soooo good, thanks bro.

[@TheTheThewillow]

You sir, great at explaining! Thanks

[@SouthBrooklynite]

Hey thanks for making this. This has been very helpful for me.

[@rajeshch9884]

Good information, thank you for the video 👌

[@milindatalwatte]

Great tutorial. Quick question: Let's assume you are turning on your computer and haven't logged in as a user yet. Do these systemd services start before the user logs in? And if they do, does that mean they run as background processes for every user available on that box?

[@tutoriaLinux]

Yeah, these services are defined at the system level, independent of any users who may or may not be logging in. Whether a user logs in (even if 0, or 100 users log in) interactively has no effect on them. That service will simply run as soon as it can (depending on when you told it to start in the unit file).

[@cheako91155]

12:50 is that a typo, or does the dash prefix mean something?

[@alessandroruggiero8932]

We need more of this, seeing the little windows icons at the too broke my heart tho 💔

[@tutoriaLinux]

I like using different OSs for different stuff! I record and game on a windows machine, work on Linux and OS X, run a variety of smaller OSs at home for fun, and manage hordes of Linux machines across the cloud. Nothing wrong with a bit of variety.

[@jindiggs]

Legend !

[@ansadahmad1958]

Hi I have a query. How do I safely make my postgresql service start only after docker service is up on boot. I need this because postgresql needs docker0 network to be up.

[@example101]

what config command or file references/finds all unit files? Are all systemd-path folders searched for unit files? Or just /etc/systemd?

[@infosandfacts7536]

Please turn down the music even more. It’s just too loud :(. Otherwise nice :)

[@mostafaali6471]

Imo it’s not that bad or maybe I’m used to working with music in the bg

[@cyberspace5317]

Quality Videos 🎸

[@tanchwa3740]

with kubernetes, I've also seen some unit files get deployed in /var/lib/systemd like etcd and the scheduler... How does this work in the grand scheme of things? If I have to backup my etcd snapshot for example or if I have to run a custom scheduler, which file do these go in ?

[@tanchwa3740]

sorry I may be mistaken. It seems some of the config locations for these SPECIFIED BY the unite files are in /var/lib/....

[@a_maxed_out_handle_of_30_chars]

Thank you ;)

[@thegorn]

Systemd is pretty sweet

[@krishnakant744]

Thank you 😊

[@poornachandumarneni1068]

Can make a comparison video on systemd-analyze and bootchart

[@prcmmd]

it was really useful

[@sammygun84]

Hi man may be you will recommend some courses on Udemy where you can prepare for junior devops after working in tech support as linux system administrator ?

[@purvashgangolli5968]

Thank you

[@martinc.7424]

Thanks a lot !👍

[@timbear64]

Do you have a version without the music?

[@veronikatolkachova4573]

why on earth would you have dark blue font in terminal... while super helpful video, thanks a lot!

[@marcschlienger973]

Interesting and helpful videos. Thank you! In another video you explained that you are using Arch even on servers. And now I saw that you are recording this video on Minibuntu running inside a virtual machine on Windows. Why? Also, it would be nice to get to know your Arch setup.

[@tutoriaLinux]

I’ve tried recording on linux machines in the past and had a terrible experience every time. It’s nice to have a separate demo VM anyway, and this way I can have it work with my Windows recording and editing setup. I run about 10 OSes at my house; I I used to be a bit more religious about my usage but have relaxed in my old age.

[@tutoriaLinux]

Forgot to add: my arch setup is relatively minimal; lightdm + i3, mostly zsh, I used to develop exclusively in emacs; now It’s a mix of things but mostly sublime text and vscode.

[@marcschlienger973]

@@tutoriaLinux Thank you for answering! For me it is the opposite: I got more religious about the software I use. But after using MacOS a couple of years I try to find my way around linux. Thats why I asked about your setup.

[@Gamer-ct6hb]

@@tutoriaLinux Are you talking in minimal as in low packages or low size? Because I'm pretty sure minimal was under 1000 lines of code. And your using Arch Linux. It uses the whole suite of systemd. Over 1 million lines of code there already. So that's just not even close to minimal.

[@sanaetagui64]

How do you save the systemd unit file please ?!

[@ramanagudluru]

Thank u so much

[@1oneguythat]

Steam updated then said i dont have 32bit library. Then got a systemd message on shutdown. File system was modified now i cant boot back into ubuntu. If it does i get a login loop. Wtf happened?

[@peterSobieraj]

I'm not sure do I like this video. I hate systemd. But I like how you explained things.

[@tutoriaLinux]

Yeah, I totally get it. I didn't write systemd, I just have to work with it :-D

[@peterSobieraj]

Back in good old days we had control over what our own computer was doing. If I wanted something to run at startup I linked it in /etc/rc5.d or /etc/rc2.d. If I wanted something to run in cron, I put it in cron. If I wanted to have specific IP I was calling ifconfig. Everything was so simple and beautiful.

[@uszr1]

Like! And thank you!

[@gregf9160]

Hiya buddy. This was really great, but audio level was _very_ low. Still loved this, though. systemd is good at killing zombie processes and that's both a good/bad thing. I'm trad Unix, and if a process misbehaves and semaphores lots of messages it ought to get killed (and possibly restarted or rescheduled, depending on the logs). What I have found, personally, systemd is a bit too lenient (at least on servers) but works _quite well_ at managing workstation processes. I still don't like the binary loggy-thang, though.

[@josephgreene630]

Audio is very good on my end.

[@KlanVinchenzo]

It still works fine for me, just volumed up a little bit. But to be fair, volume is indeed noticeably lower than other videos on this channel. That could be a problem for those watching in Linux with BT speakers, as it's a common Linux issue with a BT sounding extremely low, so you barely hear anything. For those people increasing volume to previous level would be very helpful, I assume. Thx for great channel. My only wish for you, if you find that appropriate, to use less tech words and descriptions while speaking, as we can see that $bash command for example on the screen and there is no need to pronounce it again and again. But instead I usually find myself lacking of a true meaning of what I see on the screen and more human kind description would be very helpful for better understanding. Other than that it's nearly perfect. Thank you!

[@DanielSMatthews]

Please fix your console colours, dark blue on deep purple is unreadable.

[@JudgeGideon823]

"Did you ever hear the tragedy of systemd? I thought not..."

[@Gamer-ct6hb]

You know an init is bad when there's a 14 minute video explaining it. It would literally take less time to explain the lines of code of sinit (Suckless init). And you could probably make an tutorial of every program in my system that's essential to boot ubase, sbase and sinit (Not including the Linux kernel because that's way too complicated) in the same time that this video took.

[@tourdesource]

Looking forward to those tutorials!

[@demolazer]

I feel like im a 1930s bar talking about systemd over a Martini

[@moneyteam8186]

Why do you pronounce etc as etsy?

[@tutoriaLinux]

It's faster and easier to say, and I spend a lot of time saying it.

[@peepeehammer]

nice jazz

[@littlefrank90]

The forking part you did not explain very well. The rest is very clear, thank you!

[@RaijaKaisaniemi-xi6bm]

Ja noi varkaan,ahneen algoritmit voit työntää vaikka hanuriis!

[@canerhacan]

Sound is poor :(

[@AntonioEating]

It is not guaranteed the PID of Init is 1. This is misleading information...

[@tutoriaLinux]

In what situations is init not PID1? Please elaborate. The only thing I can think of is inside a single-process docker container (running without any init process at all), the ENTRYPOINT's process would be PID1. However it's not really PID1, it only looks that way inside the container environment's process namespace (the container's PID1 would be mapped to a random high PID in the host environment).

[@MrSandshadow]

You call yourself a prefessional yet you quit vim using `:wq` instead of `:x` waisting this precious one clic!? That is just disgraceful, Sir!

[@cuszco]

Why waste an enter on `:x` when `ZZ` does the job just fine? ;)

[@JohannSuarez]

I didn't know about this. Thank you!

[@rateater420]

systemd-bloatd

[@BryanChance]

Nooooooooooooo!!!

[@_thehunter_]

your mic sucks.. very very low volume

[@pacman7168]

systemd is the worst created init

[@koolade76]

I am trying to get something to run as a service but keep messing it up. Start the process with package-name but that's under my users context. Not alway great as the process regularly goes to sleep and dies. So I tried making myservice.sh in /usr/local/bin where the package is with: #!/bin/sh package-name then a unit file in /etc/systemd/system/ as myservice.service [Unit] After=network.target [Service] User=myuser Group=groupmyuserisin ExecStart=/usr/local/bin/myservice.sh [Install] WantedBy=default.target sytemctl daemon-reload It won't start log file comes back with permission denied failed to locate excutable of .sh file. Not sure what I am doing wrong. 😕