From: Mikael Magnusson <mikachu@gmail.com>
To: Renato Botelho <rbgarga@gmail.com>
Cc: zsh-users@zsh.org
Subject: Re: tcsh set time equivalent
Date: Fri, 7 Oct 2011 18:14:31 +0200 [thread overview]
Message-ID: <CAHYJk3T7Bgf15z06vhmrUHngZM9FvCOZtJxOhbNQD-4ewQybsA@mail.gmail.com> (raw)
In-Reply-To: <CAESiWk=9no=J0MQxyCnyWQpjNeZs5fC6xpGF=zHrpH8wSWv28A@mail.gmail.com>
On 7 October 2011 18:01, Renato Botelho <rbgarga@gmail.com> wrote:
> On Fri, Sep 30, 2011 at 7:12 PM, Mikael Magnusson <mikachu@gmail.com> wrote:
>> On 30 September 2011 23:58, Renato Botelho <rbgarga@gmail.com> wrote:
>>> Hello,
>>>
>>> I used to have a configuration on tcsh:
>>>
>>> set time=(60 "\
>>> Time spent in user mode (CPU seconds) : %Us\
>>> Time spent in kernel mode (CPU seconds) : %Ss\
>>> Total time : %Es\
>>> CPU utilisation (percentage) : %P\
>>> Times the process was swapped : %W\
>>> Times of major page faults : %F\
>>> Times of minor page faults : %R")
>>>
>>> With this, if a command that took over 60s to be executed, this
>>> summary was showed after.
>>>
>>> Is there any equivalent function on zsh?
>>
>> There's REPORTTIME (just assign a number to it), but it measures cpu
>> time, not wall clock.
>
> Hello Mikael,
>
> I set REPORTTIME=2, and ran a `find /usr -type l -name '*xxxx*'`, it took
> about 20 seconds do execute and at the end, it didn't show anything.
>
> I saw zshparams manpage and this parameter is there as you said. Is there
> anything else i need to consider?
>
> I'm using zsh 4.3.11 on fedora 15
Like I said, it uses cpu time, not wall clock time. I can't imagine
find uses 2 whole cpu seconds while looking for files, so it makes
sense that it wouldn't show up.
--
Mikael Magnusson
next prev parent reply other threads:[~2011-10-07 16:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 21:58 Renato Botelho
2011-09-30 22:12 ` Mikael Magnusson
2011-10-02 2:07 ` Dan Nelson
2011-10-07 16:01 ` Renato Botelho
2011-10-07 16:14 ` Mikael Magnusson [this message]
2011-10-07 18:58 ` Renato Botelho
2011-10-07 16:51 ` Bart Schaefer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHYJk3T7Bgf15z06vhmrUHngZM9FvCOZtJxOhbNQD-4ewQybsA@mail.gmail.com \
--to=mikachu@gmail.com \
--cc=rbgarga@gmail.com \
--cc=zsh-users@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).