You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. shell-script), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you
lang-bash
$SECONDSto count time intervals. I think it's the number of seconds since the shell started, not that it matters when taking a difference.read -tor$TMOUT.$SECONDSis broken inbashandmksh.time bash -c 'while ((SECONDS < 3)); do :; done'will last in between 2 and 3 seconds. Better to use zsh or ksh93 instead here (withtypeset -F SECONDS)date +%s. Both give the time in full seconds, which does have the effect that the interval from, say, 1.9 to 4.0 looks like 3 full seconds, even though it's really 2.1. It's hard to work around that if all you can't access the fractional seconds. But yes, they should probably sleep here instead of busylooping, and thenread -tcould just as well be used. Even if you do sleep manually,time bash -c 'while [[ $SECONDS -lt 3 ]]; do sleep 1; done'works just fine.SECONDS=0ensures that$SECONDSwill reach 1 in exactly 1 second. That's not the case withbashas it usestime()to track$SECONDSinstead ofgettimeofday(). I reported bugs to mksh, zsh and bash some time ago, only zsh was fixed. (good point about the issue being the same withdate +%s). Note that it's not a busyloop here, as we're reading from the output oftail -fover a pipe.printfto emulatedatewithout external tools or command substitution:printf -v t '%(%s)T' -1.