On Thu, Jan 04, 2001 at 10:06:34PM -0600, Dave Huang wrote:
> On Thu, 4 Jan 2001, Ignatios Souvatzis wrote:
> > On Thu, Jan 04, 2001 at 12:10:26AM -0600, Dave Huang wrote:
> > > turns it back on... Boo :( (unless I kill screenblank, then the monitor
> > > comes back on). It looks like screenblank loops looking for the atime or
> > > mtime of the keyboard or mouse devices to change... what's supposed to
> > > update those in normal use? Typing on the keyboard and moving the mouse
> > > don't do it. If I do something like "touch /dev/wskbd0", that wakes the
> > > screen back up, but that's not how I want to turn on my monitor :)
> >
> > Hm, did you mount / (or /dev) with  nodevmtime ?
> 
> No, I don't have any special mount options. It looks like it works if I
> have something reading from /dev/wsmouse0. Is screenblank only supposed
> to work in X or something? I'm trying to use it with the plain text
> console, so nothing's reading wskbd0 or wsmouse0--only ttyE0 is open,
> but screenblank doesn't look at that one because it's also the
> framebuffer device (I guess if screenblank looked at ttyE0's mtime, any
> output would unblank the screen?)

Thats the behavoiur I see on Amiga. Anyway, as I use X normally, I dont use
screenblank but for testing nowadays.

Regards,
	-is