There's a PR for it (#17512), I don't think anybody has looked into it
any more. I got lost in the code trying to figure out the proper way
to update the times on the device as well. ;-)

you can probably fix screenblank so it monitors the device for input
using kqueues or another interface if you want a userspace solution
rather than checking the times for the device which is what
screenblank does.

On 5/4/05, Michael <macallan18@earthlink.net> wrote:
> Hello,
>=20
> > AFAICT this problem has been around for many years.  Something seems
> > to be fundamentally wrong with this piece of code, and somehow
> > nobody has succeeded in making it work properly.  It's not clear why
> > it cannot be made to work, and what exactly is preventing that from
> > happening.
>=20
> Sounds more like nobody bothered looking at it so far.
>=20
> > I'm guessing that part of the problem (for NetBSD) is getting the
> > screen blanking function to work across all architectures as
> > non-specifically as possible, which would probably not be that
> > straightforward.
>=20
> At least for all platforms using wscons this code would be exactly the
> same.
>=20
> > Yes, there are other more pressing matters to attend to, but this one
> > needs attention too. :-)
>=20
> Exactly :)
>=20
> > I would really like to see screenblank work properly.  I've been
> > wondering: what does everyone else out there running NetBSD do?
> > Switch of the terminal when leaving for a while?
>=20
> For instance...
>=20
> > Perhaps (I'm guessing) a lot of users rely on screen blanking as
> > provided in the X Window environment, and that's great, but what
> > about those who do _not_ use a GUI environment?  They also need the
> > screen to go blank.
>=20
> I guess most people are using X these days, and those who don't are
> probably clever enough to turn their monitors off instead of letting
> things burn in :)
>=20
> have fun
> Michael
>=20
>=20
>