Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!apple!olivea!samsung!uakari.primate.wisc.edu!dali.cs.montana.edu!ogicse!zephyr.ens.tek.com!gvgpsa!treehouse!andyp
From: andyp@treehouse.UUCP (Andy Peterman)
Newsgroups: comp.unix.aux
Subject: Re: Automatic Screen Blanking for the Login Console
Message-ID: <603@treehouse.UUCP>
Date: 19 Oct 90 05:38:06 GMT
References: <27224@shamash.cdc.com>
Organization: The Tree House
Lines: 22

In article <27224@shamash.cdc.com> jdh@punjab.udev.cdc.com () writes:
>I have found a kludgy way to get my screen blanker to automatically
>take effect when the login console is up.  We all know ........

...(some code shown here)

>This causes a dialog box to appear on the screen telling the user that
>console messages are availble.  If no one clicks the OK button, the blanker
>will turn on after its normal wait for inactivity.  Luckily, A/UX only 
>queues up two of these dialog boxes so you do not have to click several
>hundred OKs after leaving the system idle for a few hours.

Beware that this will chew up about 50% of your processor time.  Waiting
for something to happen in a modal dialog seems to use a lot of overhead.
If you have any other processes or other ways to login (such as using a
dialup or dialing out with cron), you'll find things going REAL slow.
If nothing else is going on, then it shouldn't matter.

-- 
Andy Peterman                       |   Opinions expressed
treehouse!andyp@gvgpsa.gvg.tek.com  | are definitely those of
(916) 273-4569                      |      my employer!