Recover cron jobs accidently removed with crontab -rIs it possible to recover a deleted file from crontab...

Why does Intel's Haswell chip allow FP multiplication to be twice as fast as addition?

During the Space Shuttle Columbia Disaster of 2003, Why Did The Flight Director Say, "Lock the doors."?

What are the uses and limitations of Persuasion, Insight, and Deception against other PCs?

I accidentally overwrote a Linux binary file

What gave Harry Potter the idea of writing in Tom Riddle's diary?

How are you supposed to know the strumming pattern for a song from the "chord sheet music"?

Can a fight scene, component-wise, be too complex and complicated?

Three legged NOT gate? What is this symbol?

Why should we care about syntactic proofs if we can show semantically that statements are true?

Are differences between uniformly distributed numbers uniformly distributed?

What costs less energy? Roll or Yaw?

Is refreshing multiple times a test case for web applications?

Generate Brainfuck for the numbers 1–255

Best gun to modify into a monsterhunter weapon?

Help evaluating integral (anything simple that I am missing?)

What game uses dice with sides powers of 2?

How to avoid the "need" to learn more before conducting research?

How to change a file name containing ":" in timing info

How can you evade tax by getting employment income just in equity, then using this equity as collateral to take out loan?

In a topological space if there exists a loop that cannot be contracted to a point does there exist a simple loop that cannot be contracted also?

how to differentiate when a child lwc component is called twice in parent component?

Was the 2019 Lion King film made through motion capture?

What does "sardine box" mean?

How many different ways are there to checkmate in the early game?



Recover cron jobs accidently removed with crontab -r


Is it possible to recover a deleted file from crontab -r?Finding which cron jobs are scheduled to run at some future date/time XPut two Cron jobs into crontab using wgetWhy am I seeing much more cron jobs in webmin than in `crontab -e`?cron jobs stored in /etc/cron.d work but don't display with crontab -l in RHEL4Crontab order run with differents scheduleTrouble with crontab CentOS 7 - not processing jobsCron jobs not working as expectedMonitoring of cron jobs in crontab using shell scriptcreate cron job in linux without crontab -eCron jobs present in /etc/cron.* but no cron jobs for any user?






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







62















I entered crontab -r instead of crontab -e and all my cron jobs have been removed.



What is the best way (or is there one) to recover those jobs?










share|improve this question






















  • 28





    Is it just me or wouldn't it make more sense for crontab -r to ask yes/no by default??

    – user1446688
    Feb 16 '15 at 22:54






  • 3





    I think having a yes/no prompt would be a great idea. especially since e & r are right next to each other.. and crontab -e is a really common cron command.

    – JustinP
    May 11 '15 at 15:52






  • 3





    In 7 or so years of admin work I have never had this happen to me. Now I am scared. Time to start backing up the crontabs regularly.

    – Caja
    Jun 23 '15 at 13:35






  • 6





    This has happened to me twice already. It's the worst idea ever to have e for edit and r for remove with absolutely no prompt whatsoever!!

    – DaniG2k
    Sep 7 '15 at 14:17






  • 9





    First thing to do, alias crontab=crontab -i. But crontab should have made that default, given that e & r are next to each other...

    – anishsane
    Dec 8 '15 at 6:57


















62















I entered crontab -r instead of crontab -e and all my cron jobs have been removed.



What is the best way (or is there one) to recover those jobs?










share|improve this question






















  • 28





    Is it just me or wouldn't it make more sense for crontab -r to ask yes/no by default??

    – user1446688
    Feb 16 '15 at 22:54






  • 3





    I think having a yes/no prompt would be a great idea. especially since e & r are right next to each other.. and crontab -e is a really common cron command.

    – JustinP
    May 11 '15 at 15:52






  • 3





    In 7 or so years of admin work I have never had this happen to me. Now I am scared. Time to start backing up the crontabs regularly.

    – Caja
    Jun 23 '15 at 13:35






  • 6





    This has happened to me twice already. It's the worst idea ever to have e for edit and r for remove with absolutely no prompt whatsoever!!

    – DaniG2k
    Sep 7 '15 at 14:17






  • 9





    First thing to do, alias crontab=crontab -i. But crontab should have made that default, given that e & r are next to each other...

    – anishsane
    Dec 8 '15 at 6:57














62












62








62


8






I entered crontab -r instead of crontab -e and all my cron jobs have been removed.



What is the best way (or is there one) to recover those jobs?










share|improve this question
















I entered crontab -r instead of crontab -e and all my cron jobs have been removed.



What is the best way (or is there one) to recover those jobs?







linux cron






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jun 10 '14 at 7:18









SkyDan

1,6371 gold badge13 silver badges18 bronze badges




1,6371 gold badge13 silver badges18 bronze badges










asked Jun 10 '14 at 7:12









Teerath KumarTeerath Kumar

4151 gold badge4 silver badges8 bronze badges




4151 gold badge4 silver badges8 bronze badges











  • 28





    Is it just me or wouldn't it make more sense for crontab -r to ask yes/no by default??

    – user1446688
    Feb 16 '15 at 22:54






  • 3





    I think having a yes/no prompt would be a great idea. especially since e & r are right next to each other.. and crontab -e is a really common cron command.

    – JustinP
    May 11 '15 at 15:52






  • 3





    In 7 or so years of admin work I have never had this happen to me. Now I am scared. Time to start backing up the crontabs regularly.

    – Caja
    Jun 23 '15 at 13:35






  • 6





    This has happened to me twice already. It's the worst idea ever to have e for edit and r for remove with absolutely no prompt whatsoever!!

    – DaniG2k
    Sep 7 '15 at 14:17






  • 9





    First thing to do, alias crontab=crontab -i. But crontab should have made that default, given that e & r are next to each other...

    – anishsane
    Dec 8 '15 at 6:57














  • 28





    Is it just me or wouldn't it make more sense for crontab -r to ask yes/no by default??

    – user1446688
    Feb 16 '15 at 22:54






  • 3





    I think having a yes/no prompt would be a great idea. especially since e & r are right next to each other.. and crontab -e is a really common cron command.

    – JustinP
    May 11 '15 at 15:52






  • 3





    In 7 or so years of admin work I have never had this happen to me. Now I am scared. Time to start backing up the crontabs regularly.

    – Caja
    Jun 23 '15 at 13:35






  • 6





    This has happened to me twice already. It's the worst idea ever to have e for edit and r for remove with absolutely no prompt whatsoever!!

    – DaniG2k
    Sep 7 '15 at 14:17






  • 9





    First thing to do, alias crontab=crontab -i. But crontab should have made that default, given that e & r are next to each other...

    – anishsane
    Dec 8 '15 at 6:57








28




28





Is it just me or wouldn't it make more sense for crontab -r to ask yes/no by default??

– user1446688
Feb 16 '15 at 22:54





Is it just me or wouldn't it make more sense for crontab -r to ask yes/no by default??

– user1446688
Feb 16 '15 at 22:54




3




3





I think having a yes/no prompt would be a great idea. especially since e & r are right next to each other.. and crontab -e is a really common cron command.

– JustinP
May 11 '15 at 15:52





I think having a yes/no prompt would be a great idea. especially since e & r are right next to each other.. and crontab -e is a really common cron command.

– JustinP
May 11 '15 at 15:52




3




3





In 7 or so years of admin work I have never had this happen to me. Now I am scared. Time to start backing up the crontabs regularly.

– Caja
Jun 23 '15 at 13:35





In 7 or so years of admin work I have never had this happen to me. Now I am scared. Time to start backing up the crontabs regularly.

– Caja
Jun 23 '15 at 13:35




6




6





This has happened to me twice already. It's the worst idea ever to have e for edit and r for remove with absolutely no prompt whatsoever!!

– DaniG2k
Sep 7 '15 at 14:17





This has happened to me twice already. It's the worst idea ever to have e for edit and r for remove with absolutely no prompt whatsoever!!

– DaniG2k
Sep 7 '15 at 14:17




9




9





First thing to do, alias crontab=crontab -i. But crontab should have made that default, given that e & r are next to each other...

– anishsane
Dec 8 '15 at 6:57





First thing to do, alias crontab=crontab -i. But crontab should have made that default, given that e & r are next to each other...

– anishsane
Dec 8 '15 at 6:57










3 Answers
3






active

oldest

votes


















45














crontab -r removes the only file containing the cron jobs.



So if you did not make a backup, your only recovery options are:




  • On RedHat/CentOS, if your jobs have been triggered before, you can find the cron log in /var/log/cron. The file will help you rewrite the jobs again.

  • Another option is to recover the file using a file recovery tool. This is less likely to be successful though, since the system partition is usually a busy one and corresponding sectors probably have already been overwritten.

  • On Ubuntu/Debian, if your task has run before, try grep CRON /var/log/syslog






share|improve this answer




























  • I could not voted you up but this answer was some how useful for me. thankx

    – Teerath Kumar
    Jun 10 '14 at 8:24






  • 1





    @RajaRassani You can mark the answer is a correct one with a tick mark, though. Thanks for feed back!

    – SkyDan
    Jun 10 '14 at 8:31













  • this just happened to me :) total bummer.. I do use virtual servers and backup them up regularly..so I'm going to spin up a backup.. and get the deleted crontabs

    – JustinP
    May 11 '15 at 15:49











  • +1 for being straightforward :}

    – namezero
    Apr 13 '18 at 17:54











  • You can try your luck looking for a backup made by the editor in /tmp/crontab.wpMhKS (of course the name may change). It may not be the most recent version but in my case it helped a lot

    – Jong Bor
    Aug 3 '18 at 14:11



















20














If you have no /var/log/cron file you can recover the commands (but not the timings) from the syslog.



grep 'CRON.*(yourusername)' /var/log/syslog


you can then figure out most timings by looking at the datestamps.






share|improve this answer























  • 1





    On ubuntu the file is /var/log/syslog.

    – Aurelijus Rozenas
    Nov 29 '16 at 13:02











  • @ Aurelijus Rozenas I accidentally added sys to the directory path it should be /var/log/syslog, I corrected my post.

    – Meow
    Nov 29 '16 at 17:32






  • 2





    grep 'CRON.*(yourusername)' /var/log/syslog

    – aidan
    Dec 15 '16 at 22:52













  • @Aidin you are my savior! Note to self: Never edit the crontab file while server space is full.

    – Shadoath
    Feb 6 '17 at 17:55






  • 1





    Phew that was close! I've now added a cron to backup my crontab everyday :)

    – SidJ
    Jul 5 at 6:20





















-5














vi /var/spool/cron/*user* or if you're the root user then vi /var/spool/cron/root






share|improve this answer























  • 2





    This is worse. It edits the spool files without notifying cron that the file has been edited. It also won't work when the user has accidentally deleted their crontab because there is no file to edit.

    – roaima
    Jun 23 '15 at 13:06











  • Upvote from me for actually stating the location of the crontab. I had an entire system backup and could easily retrieve my cronjobs. Thanks!

    – Cookie
    Dec 18 '15 at 14:24












protected by Michael Mrozek Jun 23 '15 at 16:36



Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



Would you like to answer one of these unanswered questions instead?














3 Answers
3






active

oldest

votes








3 Answers
3






active

oldest

votes









active

oldest

votes






active

oldest

votes









45














crontab -r removes the only file containing the cron jobs.



So if you did not make a backup, your only recovery options are:




  • On RedHat/CentOS, if your jobs have been triggered before, you can find the cron log in /var/log/cron. The file will help you rewrite the jobs again.

  • Another option is to recover the file using a file recovery tool. This is less likely to be successful though, since the system partition is usually a busy one and corresponding sectors probably have already been overwritten.

  • On Ubuntu/Debian, if your task has run before, try grep CRON /var/log/syslog






share|improve this answer




























  • I could not voted you up but this answer was some how useful for me. thankx

    – Teerath Kumar
    Jun 10 '14 at 8:24






  • 1





    @RajaRassani You can mark the answer is a correct one with a tick mark, though. Thanks for feed back!

    – SkyDan
    Jun 10 '14 at 8:31













  • this just happened to me :) total bummer.. I do use virtual servers and backup them up regularly..so I'm going to spin up a backup.. and get the deleted crontabs

    – JustinP
    May 11 '15 at 15:49











  • +1 for being straightforward :}

    – namezero
    Apr 13 '18 at 17:54











  • You can try your luck looking for a backup made by the editor in /tmp/crontab.wpMhKS (of course the name may change). It may not be the most recent version but in my case it helped a lot

    – Jong Bor
    Aug 3 '18 at 14:11
















45














crontab -r removes the only file containing the cron jobs.



So if you did not make a backup, your only recovery options are:




  • On RedHat/CentOS, if your jobs have been triggered before, you can find the cron log in /var/log/cron. The file will help you rewrite the jobs again.

  • Another option is to recover the file using a file recovery tool. This is less likely to be successful though, since the system partition is usually a busy one and corresponding sectors probably have already been overwritten.

  • On Ubuntu/Debian, if your task has run before, try grep CRON /var/log/syslog






share|improve this answer




























  • I could not voted you up but this answer was some how useful for me. thankx

    – Teerath Kumar
    Jun 10 '14 at 8:24






  • 1





    @RajaRassani You can mark the answer is a correct one with a tick mark, though. Thanks for feed back!

    – SkyDan
    Jun 10 '14 at 8:31













  • this just happened to me :) total bummer.. I do use virtual servers and backup them up regularly..so I'm going to spin up a backup.. and get the deleted crontabs

    – JustinP
    May 11 '15 at 15:49











  • +1 for being straightforward :}

    – namezero
    Apr 13 '18 at 17:54











  • You can try your luck looking for a backup made by the editor in /tmp/crontab.wpMhKS (of course the name may change). It may not be the most recent version but in my case it helped a lot

    – Jong Bor
    Aug 3 '18 at 14:11














45












45








45







crontab -r removes the only file containing the cron jobs.



So if you did not make a backup, your only recovery options are:




  • On RedHat/CentOS, if your jobs have been triggered before, you can find the cron log in /var/log/cron. The file will help you rewrite the jobs again.

  • Another option is to recover the file using a file recovery tool. This is less likely to be successful though, since the system partition is usually a busy one and corresponding sectors probably have already been overwritten.

  • On Ubuntu/Debian, if your task has run before, try grep CRON /var/log/syslog






share|improve this answer















crontab -r removes the only file containing the cron jobs.



So if you did not make a backup, your only recovery options are:




  • On RedHat/CentOS, if your jobs have been triggered before, you can find the cron log in /var/log/cron. The file will help you rewrite the jobs again.

  • Another option is to recover the file using a file recovery tool. This is less likely to be successful though, since the system partition is usually a busy one and corresponding sectors probably have already been overwritten.

  • On Ubuntu/Debian, if your task has run before, try grep CRON /var/log/syslog







share|improve this answer














share|improve this answer



share|improve this answer








edited 1 hour ago









jarhill0

1032 bronze badges




1032 bronze badges










answered Jun 10 '14 at 7:20









SkyDanSkyDan

1,6371 gold badge13 silver badges18 bronze badges




1,6371 gold badge13 silver badges18 bronze badges
















  • I could not voted you up but this answer was some how useful for me. thankx

    – Teerath Kumar
    Jun 10 '14 at 8:24






  • 1





    @RajaRassani You can mark the answer is a correct one with a tick mark, though. Thanks for feed back!

    – SkyDan
    Jun 10 '14 at 8:31













  • this just happened to me :) total bummer.. I do use virtual servers and backup them up regularly..so I'm going to spin up a backup.. and get the deleted crontabs

    – JustinP
    May 11 '15 at 15:49











  • +1 for being straightforward :}

    – namezero
    Apr 13 '18 at 17:54











  • You can try your luck looking for a backup made by the editor in /tmp/crontab.wpMhKS (of course the name may change). It may not be the most recent version but in my case it helped a lot

    – Jong Bor
    Aug 3 '18 at 14:11



















  • I could not voted you up but this answer was some how useful for me. thankx

    – Teerath Kumar
    Jun 10 '14 at 8:24






  • 1





    @RajaRassani You can mark the answer is a correct one with a tick mark, though. Thanks for feed back!

    – SkyDan
    Jun 10 '14 at 8:31













  • this just happened to me :) total bummer.. I do use virtual servers and backup them up regularly..so I'm going to spin up a backup.. and get the deleted crontabs

    – JustinP
    May 11 '15 at 15:49











  • +1 for being straightforward :}

    – namezero
    Apr 13 '18 at 17:54











  • You can try your luck looking for a backup made by the editor in /tmp/crontab.wpMhKS (of course the name may change). It may not be the most recent version but in my case it helped a lot

    – Jong Bor
    Aug 3 '18 at 14:11

















I could not voted you up but this answer was some how useful for me. thankx

– Teerath Kumar
Jun 10 '14 at 8:24





I could not voted you up but this answer was some how useful for me. thankx

– Teerath Kumar
Jun 10 '14 at 8:24




1




1





@RajaRassani You can mark the answer is a correct one with a tick mark, though. Thanks for feed back!

– SkyDan
Jun 10 '14 at 8:31







@RajaRassani You can mark the answer is a correct one with a tick mark, though. Thanks for feed back!

– SkyDan
Jun 10 '14 at 8:31















this just happened to me :) total bummer.. I do use virtual servers and backup them up regularly..so I'm going to spin up a backup.. and get the deleted crontabs

– JustinP
May 11 '15 at 15:49





this just happened to me :) total bummer.. I do use virtual servers and backup them up regularly..so I'm going to spin up a backup.. and get the deleted crontabs

– JustinP
May 11 '15 at 15:49













+1 for being straightforward :}

– namezero
Apr 13 '18 at 17:54





+1 for being straightforward :}

– namezero
Apr 13 '18 at 17:54













You can try your luck looking for a backup made by the editor in /tmp/crontab.wpMhKS (of course the name may change). It may not be the most recent version but in my case it helped a lot

– Jong Bor
Aug 3 '18 at 14:11





You can try your luck looking for a backup made by the editor in /tmp/crontab.wpMhKS (of course the name may change). It may not be the most recent version but in my case it helped a lot

– Jong Bor
Aug 3 '18 at 14:11













20














If you have no /var/log/cron file you can recover the commands (but not the timings) from the syslog.



grep 'CRON.*(yourusername)' /var/log/syslog


you can then figure out most timings by looking at the datestamps.






share|improve this answer























  • 1





    On ubuntu the file is /var/log/syslog.

    – Aurelijus Rozenas
    Nov 29 '16 at 13:02











  • @ Aurelijus Rozenas I accidentally added sys to the directory path it should be /var/log/syslog, I corrected my post.

    – Meow
    Nov 29 '16 at 17:32






  • 2





    grep 'CRON.*(yourusername)' /var/log/syslog

    – aidan
    Dec 15 '16 at 22:52













  • @Aidin you are my savior! Note to self: Never edit the crontab file while server space is full.

    – Shadoath
    Feb 6 '17 at 17:55






  • 1





    Phew that was close! I've now added a cron to backup my crontab everyday :)

    – SidJ
    Jul 5 at 6:20


















20














If you have no /var/log/cron file you can recover the commands (but not the timings) from the syslog.



grep 'CRON.*(yourusername)' /var/log/syslog


you can then figure out most timings by looking at the datestamps.






share|improve this answer























  • 1





    On ubuntu the file is /var/log/syslog.

    – Aurelijus Rozenas
    Nov 29 '16 at 13:02











  • @ Aurelijus Rozenas I accidentally added sys to the directory path it should be /var/log/syslog, I corrected my post.

    – Meow
    Nov 29 '16 at 17:32






  • 2





    grep 'CRON.*(yourusername)' /var/log/syslog

    – aidan
    Dec 15 '16 at 22:52













  • @Aidin you are my savior! Note to self: Never edit the crontab file while server space is full.

    – Shadoath
    Feb 6 '17 at 17:55






  • 1





    Phew that was close! I've now added a cron to backup my crontab everyday :)

    – SidJ
    Jul 5 at 6:20
















20












20








20







If you have no /var/log/cron file you can recover the commands (but not the timings) from the syslog.



grep 'CRON.*(yourusername)' /var/log/syslog


you can then figure out most timings by looking at the datestamps.






share|improve this answer















If you have no /var/log/cron file you can recover the commands (but not the timings) from the syslog.



grep 'CRON.*(yourusername)' /var/log/syslog


you can then figure out most timings by looking at the datestamps.







share|improve this answer














share|improve this answer



share|improve this answer








edited Dec 16 '16 at 5:41

























answered Dec 4 '15 at 21:24









MeowMeow

3412 silver badges7 bronze badges




3412 silver badges7 bronze badges











  • 1





    On ubuntu the file is /var/log/syslog.

    – Aurelijus Rozenas
    Nov 29 '16 at 13:02











  • @ Aurelijus Rozenas I accidentally added sys to the directory path it should be /var/log/syslog, I corrected my post.

    – Meow
    Nov 29 '16 at 17:32






  • 2





    grep 'CRON.*(yourusername)' /var/log/syslog

    – aidan
    Dec 15 '16 at 22:52













  • @Aidin you are my savior! Note to self: Never edit the crontab file while server space is full.

    – Shadoath
    Feb 6 '17 at 17:55






  • 1





    Phew that was close! I've now added a cron to backup my crontab everyday :)

    – SidJ
    Jul 5 at 6:20
















  • 1





    On ubuntu the file is /var/log/syslog.

    – Aurelijus Rozenas
    Nov 29 '16 at 13:02











  • @ Aurelijus Rozenas I accidentally added sys to the directory path it should be /var/log/syslog, I corrected my post.

    – Meow
    Nov 29 '16 at 17:32






  • 2





    grep 'CRON.*(yourusername)' /var/log/syslog

    – aidan
    Dec 15 '16 at 22:52













  • @Aidin you are my savior! Note to self: Never edit the crontab file while server space is full.

    – Shadoath
    Feb 6 '17 at 17:55






  • 1





    Phew that was close! I've now added a cron to backup my crontab everyday :)

    – SidJ
    Jul 5 at 6:20










1




1





On ubuntu the file is /var/log/syslog.

– Aurelijus Rozenas
Nov 29 '16 at 13:02





On ubuntu the file is /var/log/syslog.

– Aurelijus Rozenas
Nov 29 '16 at 13:02













@ Aurelijus Rozenas I accidentally added sys to the directory path it should be /var/log/syslog, I corrected my post.

– Meow
Nov 29 '16 at 17:32





@ Aurelijus Rozenas I accidentally added sys to the directory path it should be /var/log/syslog, I corrected my post.

– Meow
Nov 29 '16 at 17:32




2




2





grep 'CRON.*(yourusername)' /var/log/syslog

– aidan
Dec 15 '16 at 22:52







grep 'CRON.*(yourusername)' /var/log/syslog

– aidan
Dec 15 '16 at 22:52















@Aidin you are my savior! Note to self: Never edit the crontab file while server space is full.

– Shadoath
Feb 6 '17 at 17:55





@Aidin you are my savior! Note to self: Never edit the crontab file while server space is full.

– Shadoath
Feb 6 '17 at 17:55




1




1





Phew that was close! I've now added a cron to backup my crontab everyday :)

– SidJ
Jul 5 at 6:20







Phew that was close! I've now added a cron to backup my crontab everyday :)

– SidJ
Jul 5 at 6:20













-5














vi /var/spool/cron/*user* or if you're the root user then vi /var/spool/cron/root






share|improve this answer























  • 2





    This is worse. It edits the spool files without notifying cron that the file has been edited. It also won't work when the user has accidentally deleted their crontab because there is no file to edit.

    – roaima
    Jun 23 '15 at 13:06











  • Upvote from me for actually stating the location of the crontab. I had an entire system backup and could easily retrieve my cronjobs. Thanks!

    – Cookie
    Dec 18 '15 at 14:24
















-5














vi /var/spool/cron/*user* or if you're the root user then vi /var/spool/cron/root






share|improve this answer























  • 2





    This is worse. It edits the spool files without notifying cron that the file has been edited. It also won't work when the user has accidentally deleted their crontab because there is no file to edit.

    – roaima
    Jun 23 '15 at 13:06











  • Upvote from me for actually stating the location of the crontab. I had an entire system backup and could easily retrieve my cronjobs. Thanks!

    – Cookie
    Dec 18 '15 at 14:24














-5












-5








-5







vi /var/spool/cron/*user* or if you're the root user then vi /var/spool/cron/root






share|improve this answer















vi /var/spool/cron/*user* or if you're the root user then vi /var/spool/cron/root







share|improve this answer














share|improve this answer



share|improve this answer








edited Jun 23 '15 at 13:06









roaima

48.7k7 gold badges63 silver badges131 bronze badges




48.7k7 gold badges63 silver badges131 bronze badges










answered Jun 23 '15 at 12:39









user120610user120610

9




9











  • 2





    This is worse. It edits the spool files without notifying cron that the file has been edited. It also won't work when the user has accidentally deleted their crontab because there is no file to edit.

    – roaima
    Jun 23 '15 at 13:06











  • Upvote from me for actually stating the location of the crontab. I had an entire system backup and could easily retrieve my cronjobs. Thanks!

    – Cookie
    Dec 18 '15 at 14:24














  • 2





    This is worse. It edits the spool files without notifying cron that the file has been edited. It also won't work when the user has accidentally deleted their crontab because there is no file to edit.

    – roaima
    Jun 23 '15 at 13:06











  • Upvote from me for actually stating the location of the crontab. I had an entire system backup and could easily retrieve my cronjobs. Thanks!

    – Cookie
    Dec 18 '15 at 14:24








2




2





This is worse. It edits the spool files without notifying cron that the file has been edited. It also won't work when the user has accidentally deleted their crontab because there is no file to edit.

– roaima
Jun 23 '15 at 13:06





This is worse. It edits the spool files without notifying cron that the file has been edited. It also won't work when the user has accidentally deleted their crontab because there is no file to edit.

– roaima
Jun 23 '15 at 13:06













Upvote from me for actually stating the location of the crontab. I had an entire system backup and could easily retrieve my cronjobs. Thanks!

– Cookie
Dec 18 '15 at 14:24





Upvote from me for actually stating the location of the crontab. I had an entire system backup and could easily retrieve my cronjobs. Thanks!

– Cookie
Dec 18 '15 at 14:24





protected by Michael Mrozek Jun 23 '15 at 16:36



Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



Would you like to answer one of these unanswered questions instead?



Popular posts from this blog

Hudson River Historic District Contents Geography History The district today Aesthetics Cultural...

The number designs the writing. Feandra Aversely Definition: The act of ingrafting a sprig or shoot of one...

Ayherre Geografie Demografie Externe links Navigatiemenu43° 23′ NB, 1° 15′ WL43° 23′ NB, 1°...