* Per container uptime?
@ 2017-04-13 14:34 François
2017-04-13 16:00 ` valdis.kletnieks at vt.edu
0 siblings, 1 reply; 2+ messages in thread
From: François @ 2017-04-13 14:34 UTC (permalink / raw)
To: kernelnewbies
Hi,
after reading that post [1] on serverfault, I was wondering whether it
would make sense to implement a per container uptime.
Do you think it makes sense at all?
Any hint on how to get started on that?
Thanks
Fran?ois
[1] http://serverfault.com/questions/830643/uptime-command-gives-weird-results-in-a-docker-image
^ permalink raw reply [flat|nested] 2+ messages in thread
* Per container uptime?
2017-04-13 14:34 Per container uptime? François
@ 2017-04-13 16:00 ` valdis.kletnieks at vt.edu
0 siblings, 0 replies; 2+ messages in thread
From: valdis.kletnieks at vt.edu @ 2017-04-13 16:00 UTC (permalink / raw)
To: kernelnewbies
On Thu, 13 Apr 2017 16:34:17 +0200, Fran?ois said:
> Do you think it makes sense at all?
The bigger question is whether there's stuff that runs in a container that
wants the system uptime, which would break under this API change.
> Any hint on how to get started on that?
It's trivial - note the uptime at container creation, stash the value
in the container struct, and subtract when an uptime request happens.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 484 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20170413/7f4ed2c1/attachment.bin
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-04-13 16:00 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-04-13 14:34 Per container uptime? François
2017-04-13 16:00 ` valdis.kletnieks at vt.edu
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).