 a really cool thing called automation, like it's really just prompt, but I think it's a good thing to know for like, if you want to, if you have seen this cloud, you have some like subscription that are running, there's like a lot of things that you can simplify in your life, but you still may want the thing of like, oh, if only I could tell the computer to run this every hour, to run this every Saturday morning. And you can do that like by hand, they're like writing a demon, kind of, kind of asleep all the time or something like that, but like, like Unix people have already, no this would be good for this. Unix people have already kind of thought about that and the, the, there's like a demon running in the background, mobile, in your systems, which is called prompt, and you can say that it's running by doing something like, oh wait, yeah, okay, like root is running this thing, oh wait, you're serving prompt. And the way to kind of access what prompt can do is like doing prompt up minus E, and it will kind of drop you in this file that depending on your distribution on the brain U.S., it might be empty, or it might have something like this. I'm not even sure if this was something that came with my brain, that's called it from someone on the internet, which kind of explains the syntax of the satellite's run. So you will have like some, like five fields in the, you can see that there are like five stars in there. And the first one says the minute, the second one says the hour, the next one says the day of the month, then the one says the month, and then the last one says the week. So to give some examples, you have something like this, like asteris slash five, like asteris means all, like just like match to all of them. And asteris slash a number means match to every nth case. So for example, something like asteris slash five, like, sorry, first, if something is like all asteris, it means run every minute. And that's one of kind of the limitations of run. Like the maximum frequency you can run thinks of is one minute. But then like it's good enough for when you're most tasks. So like here are some examples, like run stuff every five minutes, run stuff every hour at like kind of peak o'clock, like at the minute zero of the hour. Then you can do like every day at 9 a.m. You can define also ranges like execute every hour, but only between hours 9 and 5 p.m. And like you can get really complex, like some tools online to kind of the, like they will, like I want to like weekday something, like they will give you a really kind of the pattern. And we can test this, like for example, we can write something like this, which is like at every minute equal like the day, the current day to this temporary file. If we do that and we go now, we can see that every minute this script has been running, just echoing, like you can see that it's either in the first second or like in the second second of the minute, and it's like outputting this. One of the in-domain things I've drawn is all like this kind of tricky to give back sometimes, because A, the maximum frequency is a minute. So maybe you realize like something is not running by default or something you haven't figured out. And the second thing is that in most distributions by default, you won't load all these like files, like we have covered like BASRC, CSRC, BAS profile. A lot of these things contain modifications to your path or they contain some modifications to your loading where some scripts are. And wrong by default doesn't know about this. It doesn't know about where these scripts are running. So you need to be careful always specifying like the full path of the script that you want to be running or like just modifying the path so the script can compile. And the other thing is like if the script doesn't work, you don't really have a way to tell that it's not working. One way to do that is to, the thing we have done here, just like redirect the output to some file that you can like file. So like some log that you can look to check the things that are working correctly or not. And even though it seems like kind of like why we need this, it can be convenient for like a lot of things. Like for example, let's say I want to do where we have this. For example, here. Oh, another good thing to do is instead of trying to run your entire command in this line, this can be like a way to maintain. Just make it execute some script. We're going to give a name script something that is more meaningful that the bunch of asterisks and appearance. So like every minute will be way easier to interpret. And if we go to the every minute script, it's doing something really simple that says, oh, if you find any file ending in txt in my downloads folder, move it to my desktop. I have like a bunch of these to say, if you find some image matching this pattern or like this red in my downloads folder, move it to this folder. Because this means I downloaded some wallpaper or I downloaded some picture from Google photos or something that I care about and soon go into that thing. So you can automate like a bunch of stuff. That's like a simple A3 file. I think what we haven't covered is also convenient is what. What does is just executes a command like continuously and like keeps refreshing every two seconds. You can specify different frequencies, but it can be convenient if you want to kind of be seeing the output of your command like again and again. And if it doesn't crack up on me, then you should like move the file when we get to kind of the whole thing. Any questions regarding, oh, and the last thing I want to mention, one bad thing about Chrome is that if the computer is off when it should fire up the command, it won't like do it. Like once like the thing comes back up online, it won't do it. So for that to here, the Chrome script movie A65 to my best. So now I have this file here because it moved automatically. The thing you want to be looking at, if you are concerned about that, like you have like something that runs pretty frequently, it's fine probably to like escape like something that runs every... Yeah. It's fine for like escape like one hour or like one minute. But you have something that runs weekly and like for some reason your computer is off, that doesn't work, that's my view of concern. And I think it's kind of this alternative that can only run I think to a maximum frequency of a day, but it will make sure to run the command or people in America will make sure that like when the computer is back up online again, it will run the command. And that's I think that like more like other tools like you can look more into this, like for example, instead of doing this Chrome thing, we cannot have look for events in the file system to kind of make it over those three years and it's like way more like we're covering kind of five minutes. But then it's good to know like from like questions. This is one of those questions where it's like just do it yourself but I get worried about running a whole bunch of these at once. Have you done that and what happened? Just like a ton of like all sorts of things like upload IPs and machines that have dynamic you don't want to use some free DNS thing and also move some files around like every second and just like what is the limitation of this? I mean the like the I have like a bunch of them have to remove them from like the demo but I do like I think like usually my A only runs to maximum frequency of a minute. So like unless you're doing like really huge tasks every minute like completely fine I have all this running all the time doing different stuff like every five minutes every hour, every morning, every night, every week. That's awesome. And yeah, for example, for stuff I think like you're talking about like if you have like dynamic DNS and you want to be kind of updating your DNS allocation every hour I think Ron is kind of the easiest thing to do instead of kind of writing your own demo and linking that to the OS. This is what I use. I don't know why this is good to know. Also one other trick people use like if you have a bunch of programs you want to run every minute instead of running them all every minute you add some offset number of seconds so like when writing the line in your current tab like for the first program we run it every minute when the second is equal like five then actually you know about it every minute when the second is equal to ten and so on and you'll see that even the recommendations for when you use like a line in your current tab for dynamic DNS they'll randomize the seconds as well I think that's more for minimizing server load or the spikes on there.