Hi Malte,
just going to chip in with my own 2 cents - your points are all valid,
except for one point. Screen is actually not too good with running
constantly refreshing backticks in my experience. It will block while
firing up the processes, rendering it unusable for a couple seconds
every n
I've been working on updating the configury for screen, and have
gotten to a state that could reasonably be merged. (Also, I don't
know that I'll have much time to look at this over the next few
months.) Primary benefits:
Uses gnulib's getloadavg, so the configury for that function is
up-to-dat
Hi Chris,
Sorry if my original post was unclear.
Some data obviously needs to be updated frequently to be useful.
My intention was to avoid the overhead of having three or four scripts
take off every second or so.
[..]
For CPU & network activity where a one-second refresh interval makes
bett
I have just solved the problem by using "*screen*" then keying in "vi txt"
thank you Matt & Florian for your kindness
:-)
On Wed, Jan 21, 2009 at 11:22 PM, Matt Mensch wrote:
> You have a typo in your command:
>
> from screen --help:
>
> -s shell Shell to execute rather than $SHELL.
> -S
