by I like having a locking screen saver, and I like the pretty displays
that DCE uses when it calls xlock, but the time to recover from a screen save
is annoyingly slow. The drive really churns away for quite some time before I
get the unlock prompt.
Worse than that, though, is what happened when I came back from the
holiday weekend this morning -- ALL modes of xlock were running simultaneously!
Multiple copies of them! It looked pretty cool, actually, but I couldn't get
the unlock prompt to save my life. I tried killing dtexec processes and then
dtscreen processes and nothing worked. I eventually had to reboot the
machine.
Anyone seen behavior like this before? I know I can avoid the problem
by just using the "blank screen" screen saver, and calling xlock directly also
seems to have fewer problems, but it'd be nice if I could get the way I'm
using it right now to work.
-------------------------------------------------------------------------
| Dan Harkless | "The sore in my soul |
-------------------------------------------------------------------------