tag:blogger.com,1999:blog-5415935778003122324.post8061032830650467325..comments2023-06-06T16:12:32.722+02:00Comments on Krisko's Blog: Replacing crontab with systemd timerskriskohttp://www.blogger.com/profile/13520273140854669947noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-5415935778003122324.post-55121140995377761792017-07-14T13:46:55.909+02:002017-07-14T13:46:55.909+02:00Thanks for sharing such a valuable information.Thi... Thanks for sharing such a valuable information.This post is very useful for me.<a href="https://ncrjobs.in/php-jobs.php" rel="nofollow">Jobs in PHP</a>Anonymoushttps://www.blogger.com/profile/10930183137220308371noreply@blogger.comtag:blogger.com,1999:blog-5415935778003122324.post-2874777925319632712016-06-02T16:36:21.924+02:002016-06-02T16:36:21.924+02:00Updated, thanks.Updated, thanks.kriskohttps://www.blogger.com/profile/13520273140854669947noreply@blogger.comtag:blogger.com,1999:blog-5415935778003122324.post-49948605831375035312016-05-27T03:13:23.850+02:002016-05-27T03:13:23.850+02:00Hi, the type of service should be oneshot, not sim...Hi, the type of service should be oneshot, not simple. Otherwise this service consistently shows up as failed.TonyMhttps://www.blogger.com/profile/04719035822159462969noreply@blogger.comtag:blogger.com,1999:blog-5415935778003122324.post-56008094502098428822015-11-01T04:10:13.084+01:002015-11-01T04:10:13.084+01:00The line:
User=%I # comment this line if you ...The line:<br />User=%I # comment this line if you want to run as root <br /><br />was giving me: <br />Failed at step USER spawning /usr/bin/php: No such process<br /><br />Oddly enough, just removing the comment fixed the problem... I don't know why :<Zeroedouthttps://www.blogger.com/profile/14080443735036773273noreply@blogger.comtag:blogger.com,1999:blog-5415935778003122324.post-68775539963621563692014-10-16T11:06:28.605+02:002014-10-16T11:06:28.605+02:00Hi, the whole point was in elimination of old cron...Hi, the whole point was in elimination of old cron way and to try out something new.<br />systemd timer also offers more options and complex configuration for jobs execution.kriskohttps://www.blogger.com/profile/13520273140854669947noreply@blogger.comtag:blogger.com,1999:blog-5415935778003122324.post-33498172896654613172014-10-15T19:42:58.869+02:002014-10-15T19:42:58.869+02:00Y U NO just use cron?Y U NO just use cron?Juan Pablo Daniel Borgnahttps://www.blogger.com/profile/14324531900736013307noreply@blogger.comtag:blogger.com,1999:blog-5415935778003122324.post-47198449979140536872014-10-07T21:40:19.875+02:002014-10-07T21:40:19.875+02:00Thanks for your fast reply. Keep up the work on th...Thanks for your fast reply. Keep up the work on the great articles including snippets on your blog!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-5415935778003122324.post-49690461406507047932014-10-07T20:44:52.557+02:002014-10-07T20:44:52.557+02:00Hi, I thing I had a problem when the user was set ...Hi, I thing I had a problem when the user was set directly, the job ran always under root... but I'm not sure, it was a while ago...<br />There is one upside thought, you can directly see which user runs which job just by listing the directory :)kriskohttps://www.blogger.com/profile/13520273140854669947noreply@blogger.com