16.12.2012 Views

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

cpio<br />

Localization<br />

Exit Values<br />

Portability<br />

cpio uses the following localization environment variable:<br />

v LANG<br />

v LC_ALL<br />

v LC_MESSAGES<br />

v LC_SYNTAX<br />

v NLSPATH<br />

See Appendix F for more information.<br />

0 Successful completion<br />

1 Failure due to any of the following:<br />

v An incorrect option<br />

v Incorrect command-line arguments<br />

v Out of memory<br />

v Compression error<br />

v Failure on extraction<br />

v Failure on creation<br />

X/Open Portability Guide, non-Berkeley <strong>UNIX</strong> systems after Version 7.<br />

The –q, –V, –y, and –z options are specific to the z/<strong>OS</strong> shell.<br />

Related Information<br />

compress, cp, dd, find, ls, mv, pax, tar, cpio, uncompress<br />

Also see the pax file format description in Appendix H.<br />

cron daemon — Run commands at specified dates and times<br />

Format<br />

Description<br />

cron<br />

cron is a clock daemon that runs commands at specified dates and times. You can<br />

specify regularly scheduled commands as described in crontab. You can also<br />

submit jobs that are to be run only once using the at command. cron runs<br />

commands with priorities and limits set by the queuedefs file. cron uses the value<br />

from queuedefs to lower the priority for non-UID=0 users only. The priority is<br />

unchanged for UID=0 users.<br />

cron only examines crontab files and at command files when initializing or when a<br />

file changes using crontab or at. This reduces the overhead of checking for new or<br />

changed files at regularly scheduled intervals.<br />

The setuid bit for cron should never be set; however, it must be started by a user<br />

with appropriate privileges to issue the setuid call for any UID. Because cron never<br />

exits, it should only be run once, normally during the system initialization process.<br />

cron automatically forks and runs itself in the background, in a new shell session.<br />

cron uses the pid file to prevent more than one cron running at the same time.<br />

168 z/<strong>OS</strong> <strong>V1R9.0</strong> <strong>UNIX</strong> <strong>System</strong> <strong>Services</strong> <strong>Command</strong> Reference

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!