supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM>
To: Supervision <supervision@list.skarnet.org>
Subject: Re: nosh: User-space virtual terminal test and questions
Date: Fri, 11 Jan 2019 05:19:56 +0000	[thread overview]
Message-ID: <b4618d37-2c00-25b4-6f37-479746393406@NTLWorld.COM> (raw)
In-Reply-To: <CADQ2Nw9COgWm6fwxnG5wzrQ3+765fMcML8_xd8X+Ux6U88OSPg@mail.gmail.com>

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

The blue/green problem only manifested itself with certain terminal 
types, which I was not regularly using.

Since you have 1.39 built, and as long as you built from today's 
snapshot, you can be the second person in the world to enjoy this:

    while true ; do printf '\f' ; top -b -n 1 | sed -e '1,6s/^/#/' ; sleep 1 ; done | console-flat-table-viewer --header-count 1

Substitute

    top -b all | sed -e '1,8s/^/#/'

on FreeBSD, or indeed

    procstat -a

Notice the |ascii| format, too.

So what the world needs now is for M. Bercot to give us a Linux+BSD 
version of |s6-ps| that uses US and RS, or |vis()| encoding.  (-:

The FreeBSD people definitely need to give us a |procstat| that uses 
|strvis()|, given that the output of |procstat| is explicitly documented 
as being a table and |vis()| encoding is actually documented for this 
type of table in FreeBSD.  (See the manual for |fstab|, for example.)


      reply	other threads:[~2019-01-11  5:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-05 20:59 Guillermo
2019-01-06 11:27 ` Jonathan de Boyne Pollard
2019-01-06 22:35   ` Guillermo
2019-01-11  0:29   ` Guillermo
2019-01-11  5:19     ` Jonathan de Boyne Pollard [this message]

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=b4618d37-2c00-25b4-6f37-479746393406@NTLWorld.COM \
    --to=j.deboynepollard-newsgroups@ntlworld.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).