All of lore.kernel.org
 help / color / mirror / Atom feed
From: aifsair@gmail.com (François)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Per container uptime?
Date: Thu, 13 Apr 2017 16:34:17 +0200	[thread overview]
Message-ID: <20170413143416.GB5209@sith> (raw)

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

             reply	other threads:[~2017-04-13 14:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-13 14:34 François [this message]
2017-04-13 16:00 ` Per container uptime? valdis.kletnieks at vt.edu

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=20170413143416.GB5209@sith \
    --to=aifsair@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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.