linux-kernel - [RFC] what should 'uptime' be on suspend?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <46A0210E.6010207@tmr.com>
Date:	Thu, 19 Jul 2007 22:42:22 -0400
From:	Bill Davidsen <davidsen@....com>
To:	Linux Kernel M/L <linux-kernel@...r.kernel.org>
Subject: [RFC] what should 'uptime' be on suspend?

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.

-- 
Bill Davidsen <davidsen@....com>
  "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/