Love your channel man, been a great resource and motivation for me as a student and a starting developer/programmer. You and Sentdex are how I learned most of what I know and why I'm able to teach similar concepts on my small channel. Thank you
Just looking at engineer man's old video and I see your comment. Now your small channel is pretty big. Kudos to you for uploading quality content consistently and making your small channel grow 👍 It's amazing how things change so fast.
Hey. I'd really appreciate you making an episode about Atom and its customisation. Like, what packages you use, what kind of custom tweaks you found useful in your day-to-day activities, something along these lines.
Another great video. Discussing @reboot cron job would have also been educational for folks but it was indicated in the excellent crontab guru you shared. Thanks for all of your efforts.
Today i had to work with cron, and if you need to hand over environment variables, its such a pain. I don't understand why this has to be that complicated... @Edit I want to execute anoter program / executable where I have no access to the source code, so I want to execute it with the enviroment variables of a given user. It looks like impossible to have a "general" approach which is working with every cronjob execute...
Can you please explain why its possible/legit to run something as different user? Shoudnt there be a passwort prompt or something? How does the security work in this case? Thank you!
Since running services as root is a bad idea, you generally want to have a low privilege service user to execute jobs for a service. Root manages cron and can execute job as any user
The scripts crontab runs are in a more restricted environment than when run on the commend line. There are very few environment variables and there is nothing connected to stdin. stdout & stderr normally go into a mail message that gets sent to the user after the job is finished.
I once applied for a Linux Cron job, they said I wasn't qualified. :-) You've made a mistake. Like the number three in Inglorious Bastards. We don't have switches, we only have options. Imposter! And camel case was great, until M$ started using it. Now it sucks. David Weeks, Tampa, Florida.
@@brister61 well, I always hear these kind of things about systemd. But fact is, that systemd is not only the future but it's already the standard in the present. Anyways, I don't quite get this systemd bashing, maybe it's because I'm still too young or so (never really, worked with cron since I always used systemd).
Thank you. I love your videos but I wish you had talked about the environment cron jobs run in, as it's different from the environment that users test their scripts in, which may cause cron jobs to fail being executed. Especially shell is different...
I also use @reboot. /Do something And also I use mon-thu for Monday through Thursday. One can also use jan-may in place of 1-5. More interesting is to only run a job on the last day of the month. Accomodate Feb with 28/29 days and months with 31 days.
@ I'd like to see stuff on gconf. Org.freedesktop stuff is confusing. Gvfs-metadata makes me nervous for security reasons..
5 лет назад
@@iamlegion990 Those are good subjects indeed. Although maybe not as relevant for developers as things in use for servers, like logrotate or crons. Did you tried kde instead of gnome? I switched like 4-5 months ago and i couldn't be happier :)
Love your channel man, been a great resource and motivation for me as a student and a starting developer/programmer. You and Sentdex are how I learned most of what I know and why I'm able to teach similar concepts on my small channel. Thank you
Just looking at engineer man's old video and I see your comment. Now your small channel is pretty big. Kudos to you for uploading quality content consistently and making your small channel grow 👍 It's amazing how things change so fast.
you have the most relaxed and clear instructions ever! amazing job!!
Hey. I'd really appreciate you making an episode about Atom and its customisation. Like, what packages you use, what kind of custom tweaks you found useful in your day-to-day activities, something along these lines.
Best explanation ever
Another great video. Discussing @reboot cron job would have also been educational for folks but it was indicated in the excellent crontab guru you shared. Thanks for all of your efforts.
Love your videos. What's your preference between systemd timers and cron jobs?
Today i had to work with cron, and if you need to hand over environment variables, its such a pain. I don't understand why this has to be that complicated...
@Edit
I want to execute anoter program / executable where I have no access to the source code, so I want to execute it with the enviroment variables of a given user. It looks like impossible to have a "general" approach which is working with every cronjob execute...
Can you please explain why its possible/legit to run something as different user? Shoudnt there be a passwort prompt or something? How does the security work in this case? Thank you!
Since running services as root is a bad idea, you generally want to have a low privilege service user to execute jobs for a service. Root manages cron and can execute job as any user
That syntax only works on the system crontab (that is owned by root), not individual user crontabs
Thanks mate
Was that the cat behind your back at 1:06? :D
That's my doggy making a guest appearance.
Haha, cool :) And thanks for the video!
The scripts crontab runs are in a more restricted environment than when run on the commend line. There are very few environment variables and there is nothing connected to stdin. stdout & stderr normally go into a mail message that gets sent to the user after the job is finished.
how do you check if a cron job ran successfully?
Redirect its output into a file and later check it. Something like:
0 20 * * * echo "cron job test" >> /home/myuser/cron_job.log
Just wanted to stop by and say thanks for all the videos that you have uploaded.
You're welcome :)
Wonderful video! Informative, right to the point, really appreciate it man.
I once applied for a Linux Cron job, they said I wasn't qualified. :-)
You've made a mistake. Like the number three in Inglorious Bastards. We don't have switches, we only have options. Imposter!
And camel case was great, until M$ started using it. Now it sucks.
David Weeks, Tampa, Florida.
But you have wrongly used correct spelling for "Inglorious Bastards". :)
Whitelisting ads on Engineer Man channel right now!
Good guy RiderOfBuffalo!
Great video as usual!
Shouldn't we use systemd timers nowadays?
systemd is the devil.
@@brister61 well, I always hear these kind of things about systemd. But fact is, that systemd is not only the future but it's already the standard in the present. Anyways, I don't quite get this systemd bashing, maybe it's because I'm still too young or so (never really, worked with cron since I always used systemd).
Very clear explanation. Thank You.
Awesome video. I never knew about [user] I instead just ran any crons as that particular user.
You forget to do a cron for first Sunday of the month... Most user fails in this one and use something similar to: 0 1 * * 7 SC.sh
If you don't know what a cron job is, you can't afford it.
Thanks for the tutorial. Very helpful.
😊
You rock thank you so much for making another linux video.
Oh yeah yeah yeah!
Thanks, very useful
Thanks for this video made perfect sense will have a play with my raspi :)
Thank you. I love your videos but I wish you had talked about the environment cron jobs run in, as it's different from the environment that users test their scripts in, which may cause cron jobs to fail being executed. Especially shell is different...
Again great tutorial
Thanks EM.
🤘
Great video. Can u please do a video about rsync?
More linux videos please !
Will u plz upload advanced python tutorials
These videos are great. I almost always use crontab.guru which is an amazing cron cheat sheet. Can you do a video on make files?
pesat
First comment
Good option to use “sudo crontab-e‘ to do it for root user
I am first
I also use @reboot. /Do something
And also I use mon-thu for Monday through Thursday. One can also use jan-may in place of 1-5.
More interesting is to only run a job on the last day of the month.
Accomodate Feb with 28/29 days and months with 31 days.
Gg
cron is B-O-R-I-NG af 🤣 kinda like logrotate
Boring but essential.
Well...logrotate is another good subject for a short video :)
@ I'd like to see stuff on gconf. Org.freedesktop stuff is confusing.
Gvfs-metadata makes me nervous for security reasons..
@@iamlegion990 Those are good subjects indeed. Although maybe not as relevant for developers as things in use for servers, like logrotate or crons. Did you tried kde instead of gnome? I switched like 4-5 months ago and i couldn't be happier :)
@ great points !!!
Thank you man