Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>NOTE: Running this as root, or using <code>sudo</code> should capture all the cron jobs on a system, not just a single users' jobs. Run it as yourself or as that user and it might capture just those jobs. I haven't test that aspect of it.</p> <hr> <p>Trying to run <code>crontab -l</code> to capture crontab files for all the users and packages seems the indirect way to do the task and could have the hassle of dealing with password requests hanging your code. I'd write code to comb through the directories that store them, rather than mess with prompts. Run the code using <code>sudo</code> and you shouldn't have any problems accessing the files.</p> <p>Take a look at the discussion at: <a href="http://www.linuxquestions.org/questions/linux-newbie-8/etc-crontab-vs-etc-cron-d-vs-var-spool-cron-crontabs-853881/" rel="nofollow noreferrer">http://www.linuxquestions.org/questions/linux-newbie-8/etc-crontab-vs-etc-cron-d-vs-var-spool-cron-crontabs-853881/</a> for information on where the actual cron tab files are stored on disk. </p> <p>Also <a href="https://superuser.com/questions/389116/how-to-recover-crontab-jobs-from-filesystem/389137">https://superuser.com/questions/389116/how-to-recover-crontab-jobs-from-filesystem/389137</a> has similar information. </p> <p>Mac OS varies a little from Linux in where Apple puts the cron files. Run <code>man cron</code> at the command-line for the definitive details on either OS.</p> <hr> <p>Here's slightly-tested code for how I'd back up the files. How you restore them is for you to figure out, but it shouldn't be hard to figure out:</p> <pre><code>require 'fileutils' BACKUP_PATH = '/path/to/some/safe/storage/directory' CRONTAB_DIRS = %w[ /usr/lib/cron/tabs /var/spool/cron /etc/anacrontab /etc/cron.d ] CRONTAB_FILES = %w[ /etc/cron_list ] def dump_pre_cron_jobs(file_path) full_backup_path = File.join( BACKUP_PATH, File.dirname(file_path) ) FileUtils.mkdir_p(full_backup_path) unless Dir.exist?(full_backup_path) File.write( File.join( full_backup_path, file_path ), File.read(file_path) ) rescue Exception =&gt; e STDERR.puts e.message end CRONTAB_DIRS.each do |ct| next unless Dir.exist?(ct) begin Dir.entries(File.join(ct, '*')).each { |fn| dump_pre_cron_jobs(fn) } rescue Errno::EACCES =&gt; e STDERR.puts e.message end end CRONTAB_FILES.each do |fn| dump_pre_cron_jobs(fn) end </code></pre> <p>You'll need to run this as root via <code>sudo</code> to access the directories and files as they're usually locked down from unauthorized prying eyes.</p> <p>The code creates a repository of crontabs, in <code>BACKUP_PATH</code>, based on their original file paths. No changes are made to the file contents so they can be restored as-is by copying them back via <code>cp</code> or writing code to reverse this process.</p>
    singulars
    1. This table or related slice is empty.
    1. PORuby Dump all cron jobs to text file
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USthe Tin Man
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COThis is assuming you want to get cron jobs for all users? What of if it's just cron jobs for the current logged on user? Would my script be ok?
      singulars
      1. PO
      1. USzulq
    2. COWell, you did say "all the existing cron jobs", not "a single user's existing cron jobs", but, run it as yourself and it might capture just you because of the way permissions work.
      singulars
      1. PO
      1. USthe Tin Man
    3. COSorry, that's a mistake on my part meant for the logged on user as the app will be deployed by a specific user. Will test your script and let you know. Thanks.
      singulars
      1. PO
      1. USzulq
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload