Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: [bug] TIMEFMT=%M reports value in mebibyte, not kibibytes

X-seq: zsh-workers 49089
From: Stephane Chazelas <stephane@xxxxxxxxxxxx>
To: Zsh hackers list <zsh-workers@xxxxxxx>
Subject: Re: [bug] TIMEFMT=%M reports value in mebibyte, not kibibytes
Date: Fri, 18 Jun 2021 21:31:56 +0100
Archived-at: <https://zsh.org/workers/49089>
In-reply-to: <20210618194848.oias7xvwvaol77bn@chazelas.org>
List-id: <zsh-workers.zsh.org>
Mail-followup-to: Zsh hackers list <zsh-workers@xxxxxxx>
References: <20210618194848.oias7xvwvaol77bn@chazelas.org>

2021-06-18 20:48:48 +0100, Stephane Chazelas:
[...]
> I have the feeling it's been discussed before (or maybe there's
> something similar going on with rlimits). It could very well be
> that there are some systems where ru_maxrss is in bytes.
[...]

It was already reported in workers/30399 in 2012.

Doc does say "some that are available may not be useful", so
one might argue we've been warned that it's not very useful...

Still the claim that %M gives kilobytes is wrong on most
systems.

-- 
Stephane

Follow-Ups:
- Re: [bug] TIMEFMT=%M reports value in mebibyte, not kibibytes
  - From: Stephane Chazelas

References:
- [bug] TIMEFMT=%M reports value in mebibyte, not kibibytes
  - From: Stephane Chazelas

Messages sorted by: Reverse Date, Date, Thread, Author