Sponsored Content
Full Discussion: What does this mean?
Top Forums Shell Programming and Scripting What does this mean? Post 302866177 by Corona688 on Monday 21st of October 2013 12:13:43 PM
Old 10-21-2013
Quote:
Originally Posted by manands07
Well it can be anything . .
I have written three scripts by now and after successful execution of each script, there's a message as shown before.
Only the field values are changing . .

Like,
5.85u 4.679s 0:16.78 105.2% 1+6k 7+8io 5pf+7w

I want to know the significance of each field . .

Thanks for reply Smilie
I'm guessing -- only guessing, mind you -- that something in your scripts is using the shell's time builtin. This can change a lot across different systems but I recognize some parts of it:

It's telling you how much time something spent running as User(5.85 seconds), as System (4.679 seconds), and a total of 16.78 seconds (so must have spent some seconds just sitting waiting for I/O).

Try time sleep 10 in your shell.

The rest I'm not sure of. I'm not even sure what the "something" was since you refuse to post your script. What's your system? uname -a if you don't know.
This User Gave Thanks to Corona688 For This Post:
 
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. IMPLEMENTATION NOTES
The SIGALRM signal is not handled specially by this implementation. The sleep command will accept and honor a non-integer number of specified seconds (with a '.' character as a decimal point). 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
All times are GMT -4. The time now is 05:28 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy