SUMMARY: xlock doesn't

From: Dave Wreski (
Date: Mon May 12 1997 - 10:23:42 CDT

Hi again. Thanks for the replies, and I got it to work..

I got it to work, but after rereading my question, and judging from the
responses, I may not have been clear as to what my problem actually was.
By 'xlock' I was speaking of the padlock-type thing that is on the CDE
task bar. (are they the same?)

Some people pointed out that xlock was insecure, and to try xlockmore
instead. Sun apparently doesn't have a fix for xlock yet..

My solution was to recreate the client credentials on the NIS+ server, and
reinitialize the client, then reboot. I must have screwed something up
when changing the root password.. I didn't want to play around with the
server on a late Sunday night.

Too bad there wasn't a quick mention of this in the Sun bug report. I
would think this should be the first thing someone does when
troubleshooting this problem..

Thanks for the help,
Dave Wreski

On Mon, 12 May 1997, Dave Wreski wrote:
> Hi all. I just set up a new box on NIS+ Solaris 2.5.1. When I try to
> lock the CDE display, I get 'dtsession: Unable to lock display due to
> security restrictions.' in my ~/.dt/errorlog. This is apparently a known
> bug, reported in #1236814, among others. The fix for them seems to be
> 0555 on /usr/dt/bin/dtsession, yet not for me.
> Leading up to this was after I created this new NIS+ client (host), I
> changed the root password and my client password (at the same time if it
> makes a difference).
> I also try to recreate the key with 'chkey -p' and rewriting the key with
> 'keylogin -r', to no avail.
> I'm pretty sure its NIS+ related, but I don't know where else to go..
> Thanks,
> Dave Wreski

This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:55 CDT