All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Ken Moffat <zarniwhoop@ntlworld.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	Linux Kernel M/L <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] what should 'uptime' be on suspend?
Date: Sat, 21 Jul 2007 09:54:37 -0400	[thread overview]
Message-ID: <46A2101D.5020400@tmr.com> (raw)
In-Reply-To: <20070720175730.GB21550@deepthought>

Ken Moffat wrote:
> On Fri, Jul 20, 2007 at 10:42:15AM -0700, Randy Dunlap wrote:
>   
>> man uptime:
>> 	uptime - tell how long the system has been running
>>
>> I claim that the system is not running when it is suspended,
>> so the suspension time should not be included in uptime.
>>
>>     
>  So, maybe I shouldn't have put corrected in inverted commas,
> because this was a real correction and my previous usage was an
> unintended side-effect of an error.
>
>  Anyway, the current behaviour is known and I guess any attempt to
> change it (e.g. to what Bill was expecting) won't be well received.
>   

So is setting it to a random number considered correct behavior? Any of 
the first three values I mentioned would make sense, but the value I see 
is neither time since resume, time since power-on to do the resume, or 
any of the logical uptime values. That was the whole point of the 
original post, the uptime reported makes no sense at all.

-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979


  parent reply	other threads:[~2007-07-21 13:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-20  2:42 [RFC] what should 'uptime' be on suspend? Bill Davidsen
2007-07-20 17:17 ` Ken Moffat
2007-07-20 17:42   ` Randy Dunlap
2007-07-20 17:57     ` Ken Moffat
2007-07-20 21:49       ` Rafael J. Wysocki
2007-07-21 13:54       ` Bill Davidsen [this message]
2007-07-21 16:29         ` Ken Moffat
2007-07-23 15:44           ` Bill Davidsen
2007-07-25 14:02         ` Pavel Machek
2007-07-25 13:59     ` Pavel Machek

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=46A2101D.5020400@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=zarniwhoop@ntlworld.com \
    /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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.