Apart from being a syntax error in ksh, this line can be replaced with the correct command to find out whether you have background processes running (the "jobs" command):
If I want a script to sleep for less than a second, would I use a decimal? In other words, if I wanted my script to sleep for 1/4 of a second, would I say, SLEEP .25 ?? (5 Replies)
Does anyone know a way to sleep less than 1 second?
Sometimes when I write scripts that iterates a loop many times it would be
nice to slow things down, but sometimes 1 second is too much. (9 Replies)
unistd.h declares the prototype of the sleep function. where is the sleep function actually defined? where is the control transfered when we include a sleep call in it?? (2 Replies)
Hi All,
Solaris
Bash v3x
I have a script that accepts an error code, and if the error code is not 0 then an email is sent using mailx to details the error.
I want to be able to implement the functiuonlity whereby i can send the email in a background process so the script can continue with... (3 Replies)
This is a very crude attempt in Bash at something that I needed but didn't seem to find in the 'sleep' command. However, I would like to be able to do it without the need for the temp file. Please go easy on me if this is already possible in some other way:
How many times have you used the... (5 Replies)
Hi,
short summary:
I need to send keystrokes from USB keyboard to background (bash-)script. I guess I have to use read on the right devive board but how and which?
My details:
I got a small home server with some VMs using KVM/Qemu, all are suse 11.3. But in general I work on a client... (0 Replies)
Hi,
I have a script that runs a process at the beginning and I want to sleep/wait until this process is finished and then continue with the rest of the script. I am trying with this, but it is not working:
process=`ps -ef | grep "proc_p01 -c" | grep -v grep | wc -l`
if ; do
sleep 10
done... (7 Replies)
Hello all,
I've a small script where it checks for the existence of a particular file and sleeps for 5 seconds if it doesn't exist. I would like to send the sleep output to background so that I don't see so many sleep messages in the build output.
#!/bin/sh -x
until
do
sleep 3
done
echo... (17 Replies)
Discussion started by: builderj
17 Replies
LEARN ABOUT FREEBSD
sleep
SLEEP(1) BSD General Commands Manual SLEEP(1)NAME
sleep -- suspend execution for an interval of time
SYNOPSIS
sleep seconds
DESCRIPTION
The sleep command suspends execution for a minimum of seconds.
If the sleep command receives a signal, it takes the standard action. When the SIGINFO signal is received, the estimate of the amount of
seconds left to sleep is printed on the standard output.
IMPLEMENTATION NOTES
The SIGALRM signal is not handled specially by this implementation.
The sleep command allows and honors a non-integer number of seconds to sleep in any form acceptable by strtod(3). This is a non-portable
extension, and its use will nearly guarantee that a shell script will not execute properly on another system.
EXIT STATUS
The sleep utility exits 0 on success, and >0 if an error occurs.
EXAMPLES
To schedule the execution of a command for x number seconds later (with csh(1)):
(sleep 1800; sh command_file >& errors)&
This incantation would wait a half hour before running the script command_file. (See the at(1) utility.)
To reiteratively run a command (with the csh(1)):
while (1)
if (! -r zzz.rawdata) then
sleep 300
else
foreach i (`ls *.rawdata`)
sleep 70
awk -f collapse_data $i >> results
end
break
endif
end
The scenario for a script such as this might be: a program currently running is taking longer than expected to process a series of files, and
it would be nice to have another program start processing the files created by the first program as soon as it is finished (when zzz.rawdata
is created). The script checks every five minutes for the file zzz.rawdata, when the file is found, then another portion processing is done
courteously by sleeping for 70 seconds in between each awk job.
SEE ALSO nanosleep(2), sleep(3)STANDARDS
The sleep command is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible.
HISTORY
A sleep command appeared in Version 4 AT&T UNIX.
BSD April 18, 1994 BSD