From owner-freebsd-current  Mon Oct 28 05:45:02 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id FAA25907
          for current-outgoing; Mon, 28 Oct 1996 05:45:02 -0800 (PST)
Received: from troll.uunet.ca (troll.uunet.ca [142.77.1.10])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA25891
          for <freebsd-current@FreeBSD.ORG>; Mon, 28 Oct 1996 05:45:00 -0800 (PST)
Received: from localhost by troll.uunet.ca with SMTP id <21003-28468>; Mon, 28 Oct 1996 08:44:49 -0500
Date: Mon, 28 Oct 1996 08:44:46 -0500
From: Cat Okita <cat@uunet.ca>
To: John Fieber <jfieber@indiana.edu>
cc: "Daniel M. Eischen" <deischen@iworks.InterWorks.org>,
        freebsd-current@FreeBSD.ORG
Subject: Re: Experiences with CDE for FreeBSD
In-Reply-To: <Pine.BSI.3.95.961025170626.20699J-100000@fallout.campusview.indiana.edu>
Message-ID: <Pine.SUN.3.93.961028084349.892q-100000@troll.uunet.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Fri, 25 Oct 1996, John Fieber wrote:
> On Thu, 24 Oct 1996, Daniel M. Eischen wrote:
> 
> > o The Screen lock and saver do not work (although the package
> >   xlockmore works just fine).  I may have something misconfigured
> >   on my end because the CDE error log file shows:
> > 
> >   "Unable to lock display due to security restrictions."
> 
> For what its worth, I get the same thing on some Solaris boxes I
> have access to.

Never had that problem with CDE - with xlock, at least, you often need to 
override the 'security' on your display, so that it will let you lock it.

Cat