1.\" Copyright (c) 1990, 1993, 1994 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" This code is derived from software contributed to Berkeley by 5.\" the Institute of Electrical and Electronics Engineers, Inc. 6.\" 7.\" Redistribution and use in source and binary forms, with or without 8.\" modification, are permitted provided that the following conditions 9.\" are met: 10.\" 1. Redistributions of source code must retain the above copyright 11.\" notice, this list of conditions and the following disclaimer. 12.\" 2. Redistributions in binary form must reproduce the above copyright 13.\" notice, this list of conditions and the following disclaimer in the 14.\" documentation and/or other materials provided with the distribution. 15.\" 3. All advertising materials mentioning features or use of this software 16.\" must display the following acknowledgement: 17.\" This product includes software developed by the University of 18.\" California, Berkeley and its contributors. 19.\" 4. Neither the name of the University nor the names of its contributors 20.\" may be used to endorse or promote products derived from this software 21.\" without specific prior written permission. 22.\" 23.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND 24.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 25.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 26.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE 27.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 28.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 29.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 30.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 31.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 32.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 33.\" SUCH DAMAGE. 34.\" 35.\" @(#)sleep.1 8.3 (Berkeley) 4/18/94 36.\" $Id$ 37.\" 38.Dd April 18, 1994 39.Dt SLEEP 1 40.Os 41.Sh NAME 42.Nm sleep 43.Nd suspend execution for an interval of time 44.Sh SYNOPSIS 45.Nm sleep 46.Ar seconds 47.Sh DESCRIPTION 48The 49.Nm sleep 50command 51suspends execution for a minimum of 52.Ar seconds . 53.Nm 54is used to schedule the execution of other commands (see 55.Sx EXAMPLES 56below). 57.Pp 58The 59.Nm 60utility exits with one of the following values: 61.Bl -tag -width flag 62.It Li \&0 63On successful completion, or if the signal 64.Dv SIGALRM 65was received. 66.It Li \&>\&0 67An error occurred. 68.El 69.Sh EXAMPLES 70To schedule the execution of a command for 71.Va x 72number seconds later: 73.Pp 74.Dl (sleep 1800; sh command_file >& errors)& 75.Pp 76This incantation would wait a half hour before 77running the script command_file. (See the 78.Xr at 1 79utility.) 80.Pp 81To reiteratively run a command (with the 82.Xr csh 1 ) : 83.Pp 84.Bd -literal -offset indent -compact 85while (1) 86 if (! -r zzz.rawdata) then 87 sleep 300 88 else 89 foreach i (`ls *.rawdata`) 90 sleep 70 91 awk -f collapse_data $i >> results 92 end 93 break 94 endif 95end 96.Ed 97.Pp 98The scenario for a script such as this might be: a program currently 99running is taking longer than expected to process a series of 100files, and it would be nice to have 101another program start processing the files created by the first 102program as soon as it is finished (when zzz.rawdata is created). 103The script checks every five minutes for the file zzz.rawdata, 104when the file is found, then another portion processing 105is done courteously by sleeping for 70 seconds in between each 106awk job. 107.Sh SEE ALSO 108.Xr at 1 , 109.Xr setitimer 2 , 110.Xr alarm 3 , 111.Xr sleep 3 112.Sh STANDARDS 113The 114.Nm sleep 115command is expected to be 116.St -p1003.2 117compatible. 118