Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!wuarchive!rice!rice!sun-spots-request
From: mikulska%odin@ucsd.edu (Margaret Mikulska)
Newsgroups: comp.sys.sun
Subject: Re: Screenblank causing panic SS1
Keywords: Miscellaneous
Message-ID: <1990Oct7.223325.27599@rice.edu>
Date: 7 Oct 90 21:30:00 GMT
Sender: sun-spots-request@rice.edu
Organization: Sun-Spots
Lines: 23
Approved: Sun-Spots@rice.edu
Originator: spots@walhalla.rice.edu
X-Sun-Spots-Digest: Volume 9, Issue 321, message 5
X-Refs:  Original: v9n314

In article <1990Sep16.130430.15551@rice.edu> elliott@shiva.trl.oz.au (Paul Elliott) writes:
>Has anybody noticed any problems with screenblank causing SS1's running
>SUNOS 4.1 to panic.  This problem occurs (not every time) at boot up time
>when screenblank is executed in rc.local, and has happened to several of
>our SS1's and an SS1+.
>
>When the machine is rebooted, all is ok. This problem did not occur when
>running SUNOS 4.0.3.

Indeed yes, I came across this one, with the same, if I recall correctly,
error mesages. What cured the problem for me was to specify time interval
as float, not integer. We have several Suns here with screenblanks, some
running 4.0, some 4.0.3, and a few 4.1. It seems that at least under 4.0
you could say "screenblank -d NNN" (for instance), but under 4.1 you have
to say "screenblank -d NNN.000". Weird. (Our screenblanks are also in
/etc/rc.local.) We certainly didn't have any more screenblank-related
panic since that small change.

Margaret Mikulska

UC San Diego
Dept. of Electrical and Computer Engineering
mikulska@mephisto.ucsd.edu