On Fri, 2003-03-07 at 19:23, Audioslave - 7M3 - Live wrote:

> 
> I haven't pined down the problem yet but if I run it with some added junk, without a
> direct path, I get the following displayed on my screen.
> 
> bash-2.05b$ time whadup
> bash: whadup: command not found
> 
> real    0m0.181s
> user    0m0.000s
> sys     0m0.000s
> bash-2.05b$ /usr/bin/time whadup
> /usr/bin/time: cannot run whadup: No such file or directory
> Command exited with non-zero status 127
> 0.00user 0.00system 0:00.02elapsed 0%CPU (0avgtext+0avgdata 0maxresident)k
> 0inputs+0outputs (25major+8minor)pagefaults 0swaps
> bash-2.05b$ /usr/bin/time --help
> Usage: /usr/bin/time [-apvV] [-f format] [-o file] [--append] [--verbose]
>        [--portability] [--format=format] [--output=file] [--version]
>        [--help] command [arg...]
> 
> Are there differnt programs called time, in different places or what? If I run time 
> with
> no parameter, without a direct path, I get some error related to the below.
> bash-2.05b$ /usr/bin/time
> Usage: /usr/bin/time [-apvV] [-f format] [-o file] [--append] [--verbose]
>        [--portability] [--format=format] [--output=file] [--version]
>        [--help] command [arg...]
> bash-2.05b$ time
> bash: syntax error near unexpected token `newline'
> 
> I am guessing that openssl has something to do with it. But as you see by my mail. I 
> know
> little about the program time. I only tried it because of the error within syncing 
> with
> up2date.
> 

You are running two different time commands.  Time, like several other
commands, exists as both a shell built-in and as a standalone program. 
The two versions have different features.  The "type" command (itself a
shell built-in) is useful to determine what will be executed:

For example, look at the following:

bash$ type time
time is a shell keyword
bash$ type cat          #demonstration of a command that's only a binary
cat is /bin/cat
bash$ help time
time: time [-p] PIPELINE
    Execute PIPELINE and print a summary of the real time, user CPU
time,
    and system CPU time spent executing PIPELINE when it terminates.
    The return status is the return status of PIPELINE.  The `-p' option
    prints the timing summary in a slightly different format.  This uses
    the value of the TIMEFORMAT variable as the output format.
bash$ /usr/bin/time --help
Usage: /usr/bin/time [-apvV] [-f format] [-o file] [--append]
[--verbose]
       [--portability] [--format=format] [--output=file] [--version]
       [--help] command [arg...]
bash$ rpm -qf /usr/bin/time
time-1.7-19


For a list of all shell built-ins, type "help" at a bash prompt. Some
other common comamnds that exist both as built-ins and standalone
binaries are test, true, false, kill, and '[' (left-bracket; same thing
as test).

Hope this helps
Jeremy



-- 
Phoebe-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/phoebe-list

Reply via email to