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.
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 ....
Comments