From: jw schultz <jw@pegasys.ws>
To: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Turning off automatic screen clanking
Date: Tue, 29 Jul 2003 22:45:43 -0700 [thread overview]
Message-ID: <20030730054543.GG9836@pegasys.ws> (raw)
In-Reply-To: <buollugep3u.fsf@mcspd15.ucom.lsi.nec.co.jp>
On Wed, Jul 30, 2003 at 11:16:05AM +0900, Miles Bader wrote:
> "Richard B. Johnson" <root@chaos.analogic.com> writes:
> > No. There are no ANSI, nor DEC nor AT&T nor IRIS, nor IBM, nor any
> > other terminals that have screen-blanking capabilities.
>
> Yes there are. I guess you never used any of them.
>
> [The brand that immediately comes to mind is Wyse, but I seem to recall
> the H29 having this capability too...]
I can't speak for the others but according to my Wyse 50
manual the S.SAVER feature in the field level 4 menu
has a default value of OFF.
My recollection is that this was common among the VDTs which
suffered considerably from burn-in. Many of the later
models had the feature but it was a hardware setting
controlled via a configuration menu or a dip-switch. You
want the setting to persist across logins and power cycling.
It really should be disabled in-kernel by default. The
distribution RC scripts would as a default then enable it
late in the boot process. In a server setting where it
isn't wanted the admin should know enough to prevent its
being enabled.
I too have been bitten by this on servers where the console
display is either powered down or disconnected for months at
a time. The error messages leading to the hang may be in
the display buffer but they can't be seen.
--
________________________________________________________________
J.W. Schultz Pegasystems Technologies
email address: jw@pegasys.ws
Remember Cernan and Schmitt
next prev parent reply other threads:[~2003-07-30 5:45 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 20:00 Turning off automatic screen clanking Richard B. Johnson
2003-07-28 20:01 ` Ben Collins
2003-07-28 20:08 ` Frank v Waveren
2003-07-28 20:25 ` Richard B. Johnson
2003-07-28 20:45 ` Charles Lepple
2003-07-29 11:06 ` Richard B. Johnson
2003-07-29 16:51 ` James Simmons
2003-07-29 17:01 ` Andries Brouwer
2003-07-29 17:54 ` Richard B. Johnson
2003-07-29 18:31 ` Alan Cox
2003-07-30 0:17 ` Zwane Mwaikambo
2003-07-30 1:25 ` Jamie Lokier
2003-07-30 1:37 ` Zwane Mwaikambo
2003-07-30 7:14 ` Alex Riesen
2003-07-30 8:00 ` David Lang
2003-07-31 14:33 ` Timothy Miller
2003-07-31 14:57 ` Zwane Mwaikambo
2003-07-31 15:20 ` Jamie Lokier
2003-07-31 21:41 ` Zwane Mwaikambo
2003-08-01 15:25 ` Jamie Lokier
2003-08-01 17:11 ` Zwane Mwaikambo
2003-07-30 1:40 ` Petr Vandrovec
2003-07-30 2:35 ` Petr Vandrovec
2003-07-30 5:22 ` Ville Herva
2003-07-30 5:44 ` Gene Heskett
2003-07-31 14:36 ` Timothy Miller
2003-07-31 16:20 ` Herbert Pötzl
2003-07-31 16:56 ` Mike Dresser
2003-07-31 19:55 ` Timothy Miller
2003-07-31 23:35 ` Ian Hastie
2003-07-30 6:03 ` jw schultz
2003-07-30 2:16 ` Miles Bader
2003-07-30 5:45 ` jw schultz [this message]
2003-07-28 20:19 ` Samuel Thibault
2003-07-28 20:27 ` Andries Brouwer
-- strict thread matches above, loose matches on Subject: below --
2003-07-29 13:02 Andries.Brouwer
2003-07-29 13:53 ` Richard B. Johnson
2003-07-29 13:56 Andries.Brouwer
2003-07-30 6:14 Erik Andersen
2003-07-30 13:07 ` Richard B. Johnson
2003-07-31 19:15 ` Norberto BENSA
2003-07-31 21:50 ` Zwane Mwaikambo
2003-07-31 20:08 Petr Vandrovec
[not found] <eFZJ.6X7.29@gated-at.bofh.it>
[not found] ` <eH5i.7XC.15@gated-at.bofh.it>
[not found] ` <eNaA.4vE.1@gated-at.bofh.it>
[not found] ` <eRHk.85K.5@gated-at.bofh.it>
[not found] ` <fmBF.48z.41@gated-at.bofh.it>
[not found] ` <fotH.5J2.17@gated-at.bofh.it>
[not found] ` <frB6.8gE.7@gated-at.bofh.it>
2003-08-03 10:40 ` Julien Oster
2003-08-04 0:56 ` Ian Hastie
2003-08-05 18:52 ` Timothy Miller
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=20030730054543.GG9836@pegasys.ws \
--to=jw@pegasys.ws \
--cc=linux-kernel@vger.kernel.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.