supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: "Johnson, Bryce" <Bryce.Johnson@landisgyr.com>
To: "supervision@list.skarnet.org" <supervision@list.skarnet.org>
Subject: timestamp or timing info for s6-rc services?
Date: Wed, 10 May 2023 17:17:33 +0000	[thread overview]
Message-ID: <PAXPR01MB9217B14DEBCA5B745726ADD8F4779@PAXPR01MB9217.eurprd01.prod.exchangelabs.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]

Hi all,
I am running s6 on buildroot with a bunch of custom services (and bundles) with dependencies.  Was there a way to turn on timestamps for s6-rc logging?  I am currently logging with -v 2 option set.  Or is there any timing information saved between a service starting and successfully started (or stopped) that I get at that is already saved somewhere?

It would be nice for some automated testing to make sure a service isn't taking much longer on a new build.  Also would be helpful to see what services were taking a long time to come up for minimizing boot time.

Thanks
Bryce


P PLEASE CONSIDER OUR ENVIRONMENT BEFORE PRINTING THIS EMAIL.

This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.

             reply	other threads:[~2023-05-10 17:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-10 17:17 Johnson, Bryce [this message]
2023-05-10 21:59 ` Laurent Bercot

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=PAXPR01MB9217B14DEBCA5B745726ADD8F4779@PAXPR01MB9217.eurprd01.prod.exchangelabs.com \
    --to=bryce.johnson@landisgyr.com \
    --cc=supervision@list.skarnet.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 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).