DOCSLIB.ORG

1.111.4 Automate System Administration Tasks by Scheduling Jobs to Run in the Future Weight 4

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
1.111.4 Automate System Administration Tasks by Scheduling Jobs to Run in the Future Weight 4 1.111.4 Automate system administration tasks by scheduling jobs to run in the future Weight 4 1.111.4 Angus Lees Automate system administration tasks by Context Objective scheduling jobs to run in the future Introduction Weight 4 at command The cron System Linux Professional Institute Certification — 102 anacron License Of This Document Angus Lees <[email protected]> Geoff Robertson <[email protected]> Nick Urbanik <[email protected]> This document Licensed under GPL—see section 7 2005 July 1.111.4 Automate system Outline administration tasks by scheduling jobs to run in the future Weight 4 Angus Lees Context Objective Introduction at Context crontab command crontab file format The cron System Objective anacron Setting up cron for root Introduction License Of This anacron Document at command anacron configuration: Specifying the time for at anacrontab The cron System License Of This Document 1.111.4 Automate system Topic 111 Administrative Tasks [21] administration tasks by Where we are up to scheduling jobs to run in the future Weight 4 Angus Lees Context Objective 1.111.1 Manage users and group accounts and related Introduction system files [4] at command 1.111.2 Tune the user environment and system The cron System environment variables [3] anacron License Of This 1.111.3 Configure and use system log files to meet Document administrative and security needs [3] 1.111.4 Automate system administration tasks by scheduling jobs to run in the future [4] 1.111.5 Maintain an effective data backup strategy [3] 1.111.6 Maintain system time [4] 1.111.4 Automate system Description of Objective administration tasks by 1.111.4 Automate system administration tasks by scheduling jobs to run in the scheduling jobs to run in the future future Weight 4 Angus Lees Context Objective Introduction at command Candidate should be able to use cron or The cron System anacron to run jobs at regular intervals and anacron License Of This to use at to run jobs at a specific time. Task Document include managing cron and at jobs and configuring user access to cron and at services. 1.111.4 Automate system 111.4 Scheduling jobs [4] administration tasks by Key files, terms and utilities scheduling jobs to run in the future Weight 4 Angus Lees at Context crontab Objective atq Introduction at command /etc/anacrontab The cron System /etc/at.deny anacron License Of This /etc/crontab Document /etc/at.allow /etc/cron.allow /etc/cron.deny /var/spool/cron/* 1.111.4 Automate system Basically administration tasks by scheduling jobs to run in the future Weight 4 Angus Lees Context Objective Introduction at command The cron System anacron I at – Run a command once License Of This I cron – Run a command periodically Document 1.111.4 Automate system The at command administration tasks by scheduling jobs to run in the future Weight 4 Angus Lees Context at takes a time and a list of commands to run. Any output to Objective STDOUT or STDERR will be mailed to the user running at. Introduction at command Specifying the time for at The cron System anacron $ at 2pm ←- License Of This warning: commands will be executed using /bin/sh Document at> date ←- at> ^D ←- job 3 at 2002-05-08 14:00 1.111.4 Automate system The at command administration tasks by scheduling jobs to run in the future Weight 4 Angus Lees Context Objective Introduction at command The current umask, working directory and environment (except Specifying the time for at for TERM, DISPLAY and _) are saved and restored before The cron System anacron cron running the job (unlike ). License Of This Document The commands to run will be read from STDIN or from a file given with -f . 1.111.4 Automate system Example at time specifications administration tasks by scheduling jobs to run in the future Weight 4 Angus Lees Context at allows a very flexible time format. Objective Introduction at command Specifying the time for at 17:36 Run at 5:36pm today or tomorrow. The cron System 9pm May 8 Run at 9pm on May 8th. anacron License Of This noon tomorrow Run at 12pm tomorrow. Document now + 2 hours Run in 2 hours. See at(1) for more details. 1.111.4 Automate system Queued jobs administration tasks by scheduling jobs to run in the future Weight 4 Angus Lees Context Objective atq lists a user’s pending jobs. Introduction at command $ atq ←- Specifying the time for at 3 2002-05-08 14:00 a gus The cron System anacron License Of This Document $ atrm 3 ←- removes the queued job. $ at -c 3 ←- dumps the job on STDOUT. 1.111.4 crontab Automate system administration tasks by scheduling jobs to run in the future Weight 4 Angus Lees Context Objective Introduction crond is a daemon that reads everyone’s crontab at command information, spawning new tasks at the appropriate times. The cron System crontab crontab file Replace your crontab file with file. crontab file format Setting up cron for root crontab -l List your crontab. anacron crontab -r Remove your crontab. License Of This Document crontab -e Edit your crontab (with $EDITOR). 1.111.4 Automate system crontab file format administration tasks by scheduling jobs to run A sample crontab file: in the future Weight 4 0 7 1 jan * echo "sleep in, you dont feel so good" Angus Lees # gratuitous noise Context 0 17 ** mon,wed,fri wall%meeting in 5 minutes% Objective 0 9-18/2 ** mon-fri $HOME/bin/cron.bihourly Introduction Line based, hash comments, ignored blank lines, etc at command The cron System I Minute (0-59) crontab crontab file format I Hour (0-23) Setting up cron for root anacron I Day of month (1-31) License Of This I Month (1-12 or jan-dec) Document I Day of week (0-7 or sun-sat) I Step I Wildcard I Ranges I Lists See crontab(5) for: I Environment variables I Providing STDIN 1.111.4 Automate system cron from root administration tasks by scheduling jobs to run in the future Weight 4 Angus Lees A few extra issues arise when editing /etc/crontab (and similar “system” crontab files): Context Objective crontab -e /etc/crontab I Don’t use , edit directly. Introduction I A new column (after timespec, before command) gives the at command user to the command run as. The cron System crontab crontab file format I Distributions often create directories for “common” Setting up cron for root frequencies. It usually makes much more sense to place a anacron script in there, rather than adding your own crontab lines. License Of This Debian, Red Hat runs any scripts in Document /etc/cron.{daily,weekly,monthly} – but these are triggered from normal entries in /etc/crontab, so there’s no real mystery here. I /etc/cron.d/* is read in addition to /etc/crontab (they also have the extra user field). 1.111.4 anacron Automate system administration tasks by scheduling jobs to run in the future Weight 4 Angus Lees Context Objective Introduction Apparently some people turn their machines off. at command The cron System If your computer is always turned off at night (for example), anacron anacron configuration: then daily jobs which are usually scheduled to run in the wee anacrontab hours, will never be run. This is a problem. License Of This Document anacron fixes this by running any missed jobs after a reboot (or other times, like AC-on for laptops). 1.111.4 Automate system anacron configuration: anacrontab administration tasks by scheduling jobs to run in the future Weight 4 Angus Lees Context Objective Introduction Since anacron can’t use the crontab files, it has its own at command simplified /etc/anacrontab. The cron System anacron anacron configuration: If you only use the standard anacrontab /etc/cron.daily,monthly,weekly, then no further License Of This Document configuration will be necessary. Otherwise, see anacrontab(5). Note that the frequency of anacron jobs can only be specified in days. 1.111.4 Automate system Topics Covered administration tasks by scheduling jobs to run in the future Weight 4 Context Angus Lees Context Objective Objective Introduction Introduction at command The cron System at command anacron at anacron configuration: Specifying the time for anacrontab License Of This The cron System Document crontab crontab file format Setting up cron for root anacron anacron configuration: anacrontab License Of This Document 1.111.4 Automate system License Of This Document administration tasks by scheduling jobs to run in the future Weight 4 Angus Lees Context Objective Copyright c 2005, 2003 Angus Lees <[email protected]>, Introduction Geoffrey Robertson <[email protected]> and Nick Urbanik at command <[email protected]>. The cron System Permission is granted to make and distribute verbatim copies anacron License Of This or modified versions of this document provided that this Document copyright notice and this permission notice are preserved on all copies under the terms of the GNU General Public License as published by the Free Software Foundation—either version 2 of the License or (at your option) any later version..
Load more

Recommended publications
  • Oracle® Linux 7 Monitoring and Tuning the System
    Oracle® Linux 7 Monitoring and Tuning the System F32306-03 October 2020 Oracle Legal Notices Copyright © 2020, Oracle and/or its affiliates. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.
    [Show full text]
  • Taskplaner 123RF ©Everydayplus
    Know-how Cron-Alternativen Moderne Task-Scheduler: Fcron und Hcron Taskplaner 123RF ©everydayplus, Der Standard-Scheduler Cron Die meisten Rechner laufen nicht rund der nach dem Einschalten des Compu- um die Uhr, schon um Strom zu sparen. ters offene Routineaufgaben nachholt. ist inzwischen leicht ange- Trotzdem will man manche Aufgaben Dazu haben wir unter Fedora 29 die automatisiert in Zeiten abarbeiten, zu Scheduler Fcron und Hcron an- staubt. Mit Fcron und Hcron denen man nicht vor dem Computer hand des Programms Backup-Mana- sitzt: Es ist auf die Dauer mühsam, stän- ger auf Herz und Nieren getestet. gibt es modernere Alternati- dig das Backup manuell zu starten. Mit Die Konfiguration von Hcron behan- dem klassischen Scheduler Cron lassen delte bereits unsere Schwesterzeitschrift ven, jeweils mit spezifischen sich derartige Tasks automatisiert abwi- Raspberry Pi Geek ausführlich . Daher ckeln. Läuft allerdings zum vorgegebe- widmet sich dieser Artikel vorwiegend Anzela Minosi Vorteilen. nen Zeitpunkt der PC nicht, fällt die auto- Fcron, um zum Schluss die Vor- und matische Ausführung unter den Tisch. Nachteile beider Scheduler abzuwägen. Regelmäßige Aufgaben sollten Sie da- her lieber einem Scheduler überlassen, Listing 2 # dnf install python3 Listing 1 python3‑PyQt5 python3‑PyQt4 # dnf install gcc sendmail [...] [...] $ wget https://downloads. README $ wget http://fcron.free.fr/ sourceforge.net/project/fcronq/ FcronQ/0.5.0/FcronQ‑0.5.0.tar.bz2 Sowohl Hcron als auch Fcron eignen sich archives/fcron‑3.2.1.src.tar.gz $ tar xvf fcron‑3.2.1.src.tar.gz $ tar xvf FcronQ‑0.5.0.tar.bz2 für Computer, die nicht nonstop laufen. $ cd fcron‑3.2.1 $ cd FcronQ/Build/ Beide können Aufgaben planen und regel- $ ./configure $ make all $ make install‑user mäßig ausführen, für Fcron gibt es dazu so- $ gmake [...] [..
    [Show full text]
  • Questions for Delayed Execution - Cron, At, Sleep
    www.YoYoBrain.com - Accelerators for Memory and Learning Questions for Delayed execution - cron, at, sleep Category: all - (15 questions) Purpose of cron schedule tasks to run periodically in the future, can be daily, monthly, etc. Version of cron designed for systems that anacron aren't up 24x7 What tells cron when to run tasks crontab entries that are stored in cron schedule Command used to schedule one-time at processes that need to run at some point in future What is the format of each entry in crontab mins hrs day-of-month month weekday file command What is the syntax for a crontab entry to run 0,15,30,45 * * * * cmd cmd every 15 minutes entries can be comma separated What is crontab syntax to run cmd on the 1st 30 3 1-15 * * cmd day of month through 15th day at 3:30 am What directories in /etc are provided to make cron.daily creating daily, hourly, monthly, and weekly cron.hourly tasks easier on some systems cron.monthly cron.weekly How do you upload a schedule to crontab create a file with the crontab entries then system run: crontab filename it will overwrite any existing entries How do you get a list of current crontab crontab -l entries How do you remove all current crontab crontab -r entries How do you edit current crontab entries crontab -e directly How can you see what jobs have been atq (at queue) scheduled with command at Command to remove a command that has atrm been scheduled with at Command that simply waits a set amount of sleep seconds time.
    [Show full text]
  • Bash Guide for Beginners
    Bash Guide for Beginners Machtelt Garrels Xalasys.com <tille wants no spam _at_ xalasys dot com> Version 1.8 Last updated 20060315 Edition Bash Guide for Beginners Table of Contents Introduction.........................................................................................................................................................1 1. Why this guide?...................................................................................................................................1 2. Who should read this book?.................................................................................................................1 3. New versions, translations and availability.........................................................................................2 4. Revision History..................................................................................................................................2 5. Contributions.......................................................................................................................................3 6. Feedback..............................................................................................................................................3 7. Copyright information.........................................................................................................................3 8. What do you need?...............................................................................................................................4 9. Conventions used in this
    [Show full text]
  • Running Jobs Unattended by Jerry Peek
    POWER TOOLS Running Jobs Unattended By Jerry Peek inux systems have several ways to run jobs unattended at % (sleep 14400; xmessage -near Meet Jim) & L some later time — either once or many times. Scheduling jobs in the future is handy for system mainte- The shell silently runs sleep for 14,400 seconds, and then nance, for sending yourself reminders, and for making more runs xmessage. practical and efficient use of your CPU by running jobs Using sleep has advantages over cron and at (we’ll look at when users are away. cron and at momentarily). For instance, since sleep is typical- As usual though, there are gotchas: if you want to run ly used in a shell window (like xterm), it can open other win- multiple commands or run commands that need a particular dows. Other techniques can’t open windows because they setup (including environment variables, a tty, or a certain aren’t run from your terminal under X. current directory), or want to avoid system overload, you need to know a few tricks. This month, let’s dig into job at: Doing It at a Later Time scheduling systems, discuss the potential problems, and find some answers. The at utility queues one or more commands to run at some time in the future. A daemon (or a special cron job) runs jobs Catching some Zs submitted by at. Using at, you can schedule jobs to run minutes or months An easy way to delay execution is with the sleep command. into the future. Typically, you put the job time on the com- sleep simply waits for some number of seconds (for instance, mand line, and enter the commands to run on at’s standard sleep 60 waits sixty seconds) and then exits.
    [Show full text]
  • Cron, Anacron, at Cron
    Scheduling Jobs: cron, anacron, at cron jboydt :: csci 26 | cron, anacron, at What is cron? ● a daemon ● a job scheduler ● a way to run both: ○ system cron jobs ■ run as root, for system-wide maintenance ○ user cron jobs ■ run as a specified user jboydt :: csci 26 | cron, anacron, at How do I use cron? ● /etc/crontab (system cron jobs) ● crontab (utility, user cron jobs) ○ crontab -u USER -l (list current crontab for USER) ○ crontab -u USER -e (edit current crontab for USER) ○ crontab -u USER -r (remove current crontab for USER) jboydt :: csci 26 | cron, anacron, at What does a cron entry look like? jboydt :: csci 26 | cron, anacron, at What does a cron entry look like? ● 7 fields minute hour day month day-of-week user command (0-59) (0-23) (1-31) (1-12)* (0-7) ● month and day-of-week can be specified using first three letters (e.g., Dec, Wed) ● 0 and 7 for day-of-week are both Sunday ● an asterisk (*) in a field means all available (e.g., a * for day field means every day) ● use a dash (-) to specifiy a range (e.g., 1-6 for month means January through February) ● use a slash (/) to specify increments (e.g., */15 for minutes means every 15 minutes) ● use commas to specify multiple values (e.g., 1,3,5 for day-of-week means Mon, Wed, Fri) jboydt :: csci 26 | cron, anacron, at What does a cron entry look like? ● some examples 0 12 * * * root SOME_SCRIPT (midnight every day) */30 * * * 1,3,5 janedoe SOME_SCRIPT >> /home/janedoe/LOGFILE (every 30 minutes on Mon, Wed, Fri) 0 0 1 * * root SOME_SCRIPT (midnight on the first day of every month)
    [Show full text]
  • Model Checking an Entire Linux Distribution for Security Violations
    Model Checking An Entire Linux Distribution for Security Violations by Benjamin W. Schwarz Research Project Submitted to the Department of Electrical Engineering and Computer Sciences, University of California at Berkeley, in partial satisfaction of the requirements for the degree of Master of Science, Plan II. Approval for the Report and Comprehensive Examination: Committee: David Wagner Research Advisor (Date) * * * * * * * Doug Tygar Second Reader (Date) Abstract Software model checking has become a popular tool for verifying pro- grams’ behavior. Recent results suggest that it is viable for finding and erad- icating security bugs quickly. However, even state-of-the-art model checkers are limited in use when they report an overwhelming number of false positives, or when their lengthy running time dwarfs other software development pro- cesses. In this paper we report our experiences with software model checking for security properties on an extremely large scale—an entire Linux distribu- tion consisting of 839 packages and 60 million lines of code. To date, we have discovered 108 exploitable bugs. Our results indicate that model checking can be both a feasible and integral part of the software development process. 2 Contents 1 Introduction 5 2 The MOPS Model Checker 6 2.1 Specification of Security Properties . 7 2.2 Scalability . 8 2.3 Error Reporting . 8 2.4 Efficient Model Checking with Pattern Variables . 9 2.4.1 Current implementation . 9 2.4.2 More Efficient Algorithms . 10 2.5 User Interface for Error Reporting . 11 2.6 Resource Usage . 12 3 Checking Security Properties 12 3.1 TOCTTOU . 13 3.2 A Standard File Descriptor Attack .
    [Show full text]
  • Automated Malware Analysis Report for Anacron
    ID: 202040 Sample Name: anacron Cookbook: defaultlinuxfilecookbook.jbs Time: 02:46:46 Date: 20/01/2020 Version: 28.0.0 Lapis Lazuli Table of Contents Table of Contents 2 Analysis Report anacron 5 Overview 5 General Information 5 Detection 5 Classification 5 Mitre Att&ck Matrix 6 Signature Overview 7 AV Detection: 7 Bitcoin Miner: 7 Networking: 7 System Summary: 7 Persistence and Installation Behavior: 7 Malware Analysis System Evasion: 7 Malware Configuration 8 Runtime Messages 8 Behavior Graph 8 Yara Overview 8 Initial Sample 8 PCAP (Network Traffic) 9 Dropped Files 9 Sigma Overview 9 Joe Sandbox View / Context 9 IPs 9 Domains 9 ASN 9 JA3 Fingerprints 10 Dropped Files 10 Antivirus, Machine Learning and Genetic Malware Detection 10 Initial Sample 10 Dropped Files 10 Domains 10 URLs 10 Startup 10 Created / dropped Files 11 Domains and IPs 12 Contacted Domains 12 URLs from Memory and Binaries 12 Contacted IPs 12 Public 13 Static File Info 13 General 13 Static ELF Info 13 ELF header 13 Sections 14 Program Segments 14 Dynamic Tags 14 Symbols 15 Network Behavior 15 Network Port Distribution 15 TCP Packets 15 UDP Packets 15 DNS Queries 15 DNS Answers 15 System Behavior 16 Analysis Process: anacron PID: 20758 Parent PID: 20706 16 General 16 File Activities 16 File Read 16 Copyright Joe Security LLC 2020 Page 2 of 23 Directory Enumerated 16 Analysis Process: anacron PID: 20759 Parent PID: 20758 16 General 16 Analysis Process: sh PID: 20759 Parent PID: 20758 16 General 16 File Activities 17 File Read 17 File Written 17 Analysis Process: sh PID:
    [Show full text]
  • Linux Quick Reference Guide (8Th Ed.)
    Linux Quick Reference Guide 8th edition January 2020 Foreword This guide stems from the notes I have been taking while studying and working as a Linux sysadmin and engineer. It contains useful information about standards and tools for Linux system administration, as well as a good amount of topics from the certification exams LPIC-1 (Linux Professional Institute Certification level 1), LPIC-2, RHCSA (Red Hat Certified System Administrator), and RHCE (Red Hat Certified Engineer). Unless otherwise specified, the shell of reference is Bash. This is an independent publication and is not affiliated with LPI or Red Hat. You can freely use and share the whole guide or the single pages, provided that you distribute them unmodified and not for profit. This document has been composed with Apache OpenOffice. Happy Linux hacking, Daniele Raffo Version history 1st edition May 2013 2nd edition September 2014 3rd edition July 2015 4th edition June 2016 5th edition September 2017 6th edition August 2018 7th edition May 2019 8th edition January 2020 Bibliography and suggested readings ● Evi Nemeth et al., UNIX and Linux System Administration Handbook, O'Reilly ● Rebecca Thomas et al., Advanced Programmer's Guide to Unix System V, McGraw-Hill ● Mendel Cooper, Advanced Bash-Scripting Guide, http://tldp.org/LDP/abs/html ● Adam Haeder et al., LPI Linux Certification in a Nutshell, O'Reilly ● Heinrich W. Klöpping et al., The LPIC-2 Exam Prep, http://lpic2.unix.nl ● Michael Jang, RHCSA/RHCE Red Hat Linux Certification Study Guide, McGraw-Hill ● Asghar Ghori, RHCSA & RHCE RHEL 7: Training and Exam Preparation Guide, Lightning Source Inc.
    [Show full text]
  • Ubuntu: Powerful Hacks and Customizations
    Hacks, tips, and tricks to Krawetz put your OS into overdrive ubuntu Whether it’s speed, glitz, sounds, or security, you want to get the most out of your Ubuntu Linux system. This book shows you how to do just that. You’ll fi nd out how to customize the user interface, implement networking tools, optimize video, and more. You’ll then be able to build on these hacks to further tune, tweak, and customize Ubuntu to meet all your needs. The basic Ubuntu system is good, but with a few modifi cations, it can be made great. This book is packed with techniques that will help you: • Choose the right options when installing Ubuntu onto a Netbook, server, or other system • Install fi les for interoperability and collaborate with non-Linux systems • Tune the operating system for optimal performance ® • Enhance your graphics to take them to the next level Powerful Hacks and Customizations Powerful • Navigate the desktop, manage windows, and multitask between applications • Check for vulnerabilities and prevent undesirable access • Learn tricks to safely opening up the system with external network services Neal Krawetz, PhD, is a computer security professional with experience in computer forensics, ® profi ling, cryptography and cryptanalysis, artifi cial intelligence, and software solutions. Dr. Krawetz’s company, Hacker Factor, specializes in uncommon forensic techniques and anti-anonymity technologies. He has confi gured Ubuntu on everything from personal workstations to mission-critical servers. ubuntu Visit our Web site at www.wiley.com/compbooks $39.99 US/$47.99 CAN Powerful Hacks and Customizations ISBN 978-0-470-58988-5 Neal Krawetz Operating Systems / Linux Ubuntu® Powerful Hacks and Customizations Dr.
    [Show full text]
  • Oracle® Linux 8 Monitoring and Tuning the System
    Oracle® Linux 8 Monitoring and Tuning the System F24025-08 August 2021 Oracle Legal Notices Copyright © 2019, 2021 Oracle and/or its affiliates. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.
    [Show full text]
  • Cron Job, Crontab -E, -L Using
    cron job, crontab -e, -l using Cron Job Timing , Advanced Crontab The Crontabs discussed above are user crontabs. Each of the above crontabs is associated with a user, even the system crontab which is associated with the root user. There are two other types of crontab. Firstly, as mentioned above anacron uses the run-parts command and /etc/cron.hourly, /etc/cron.weekly, and /etc/cron.monthly directories. However anacron itself is invoked from the /etc/crontab file. This file could be used for other cron commands, but probably shouldn’t be. Here’s an example line from a ficticious /etc/crontab: [crayon-614fca573b3f4010762206/] This would run Rusty’s command script as user rusty from his home directory. However, it is not usual to add commands to this file. While an experienced user should know about it, it is not recommended that you add anything to/etc/crontab . Apart from anything else, this could cause problem if the /etc/crontab file is affected by updates! Rusty could lose his command. The second type of crontab is to be found in/etc/cron.d . Within the directory are small named crontabs. The directory is often used by packages, and the small crontabs allows a user to be associated with the commands in them. Instead of adding a line to /etc/crontab which Rusty knows is not a good idea, Rusty might well add a file to /etc/cron.d with the name rusty, containing his cron line above. This would not be affected by updates but is awell known location. When would you use these alternate crontab locations? Well, on a single user machine or a shared machine such as a school or college server, auser crontab would be the way to go.
    [Show full text]