Tag Info

Hot answers tagged

7

By default, watch runs your command with /bin/sh -c '...' so the output you see is how /bin/sh interprets the time command. Your /bin/sh apparently doesn't have a builtin time. To run the command with a different shell, use the -x option to get rid of the default, then add your own explicit invocation of the shell whose builtin you want. watch -x bash -c ...


2

Mac OS X doesn't ship with the GNU stack. You have "BSD Time" time.c,v 1.9. You can verify this by typing: strings /usr/bin/time | grep c,v BSD time doesn't support --verbose, but it does support /usr/bin/time -lp: $ /usr/bin/time -lp echo hi hi real 0.02 user 0.00 sys 0.00 700416 maximum resident set size 0 ...


2

When you invoke a command without specifying path to it, others shell alias, function, builtin with the same name will be invoked, instead of command. This behavior was defined by POSIX. In order to call external time command, you can use command: command time --verbose cmd


2

Because /usr/bin/time and the time build into your shell are completely different implementations. Run help time to get the usage of the one built into your shell, and obviously man time for the one in /usr/bin/time.


1

I guess that your OS is some flavor of Linux. Be sure that your $DD/batchfile.batch file exists and is readable & executable. I believe that your batch(1) job is started. Perhaps it is exited quickly (e.g. because the PATH for batch jobs is perhaps not your interactive PATH, or because your environment is not the same as in interactive shells - see ...



Only top voted, non community-wiki answers of a minimum length are eligible