All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ken Moffat <zarniwhoop@ntlworld.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Linux Kernel M/L <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] what should 'uptime' be on suspend?
Date: Fri, 20 Jul 2007 18:17:29 +0100	[thread overview]
Message-ID: <20070720171729.GA19935@deepthought> (raw)
In-Reply-To: <46A0210E.6010207@tmr.com>

On Thu, Jul 19, 2007 at 10:42:22PM -0400, Bill Davidsen wrote:
> I just found a machine which will resume after suspend to memory, using 
> the mainline kernel (no suspend2 patch).
> 
> On resume I was looking at the uptime output, and it was about six 
> minutes, FAR longer than the time since resume. So the topic for 
> discussion is, should the uptime be
> - time sine the original boot
> - total uptime since first boot, not counting the time suspended
> - time since resume
> - some other time around six minutes
> 
> Any of the first three could be useful and "right" for some casesm thus 
> discussion invited.
> 
 My ibook has always been able to suspend to RAM.  For a long while,
uptime was shown as the time since the last boot.  At some point,
maybe about a year ago, this was "corrected" to show time since boot
_less_ time suspended.

 To be clear, the ibook suspends when I close the lid and resumes
when I open it.  Uptime used to be convenient, because I could work
out when I'd last booted.

Ken
-- 
das eine Mal als Tragödie, das andere Mal als Farce

  reply	other threads:[~2007-07-20 17:29 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 [this message]
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
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=20070720171729.GA19935@deepthought \
    --to=zarniwhoop@ntlworld.com \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.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.
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.