Skip to main content

Linux tip: Job scheduling with cron and at.

You need to run a job at midnight when system usage is low, or you need to run jobs daily or weekly, but you would rather be sleeping, or enjoying life in some other way. Other good reasons for scheduling jobs include letting routine tasks happen automatically, or ensuring tasks are handled the same way every time. This tip helps you use the cron and at capabilities to schedule jobs periodically or at a single future time.

Comments

Popular posts from this blog

Fixing Unix/Linux/POSIX Filenames

Traditionally, Unix/Linux/POSIX filenames can be almost any sequence of bytes, and their meaning is unassigned. The only real rules are that "/" is always the directory separator, and that filenames can't contain byte 0 (because this is the terminator). Although this is flexible, this creates many unnecessary problems. In particular, this lack of limitations makes it unnecessarily difficult to write correct programs (enabling many security flaws), makes it impossible to consistently and accurately display filenames, causes portability problems, and confuses users. more ....

Multi-Boot Disk for Machines With AMD Opteron Processors

This article presents step-by-step procedures for loading the Solaris 10 OS on x86 platforms, and one or two 64-bit Linux operating systems, on machines based on 64-bit AMD Opteron processors. Installations were done on generic Opteron-based workstations and confirmed on a Sun Fire V20z server and Sun Java Workstation W1100z and W2100z workstations.

Application configuration with Perl.

File-based configurations break down quickly if you use a hand-built method. Teodor Zlatanov demonstrates how the AppConfig module can handle local configuration storage for Perl programs, and how such configurations can be stored in a database that can then be accessed from any machine on the network. more .