Yup, that's the problem. xlock doesn't behave if it's not setuid-root. :( xscreensaver (on the other hand) complains if it's not setuid-root, but at least it yields the correct functionality...
Thanks, Anthony -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alan Coopersmith Sent: September-17-08 12:27 PM To: SunRay-Users mailing list Subject: Re: [SunRay-Users] xlock problem SRSS 4.0 Anthony Winstanley wrote: > We’re having problems getting xlock to work on SRSS 4.0 running on > Solaris 10 (sparc). > > Running /usr/openwin/bin/xlock on the command line gives: > Xlib: connection to “:9.0” refused by server > Xlib: Client is not authorized to connect to Server > xlock: unable to open display :9.0. > > If I “xhost +localhost”, it works, but that’s not a proper solution. > Other apps work without adding localhost to the xhost list, and the > Xauthority seems to be set right... xlock is setuid root (so that it can access /etc/shadow for authenticating users defined in local /etc files) - are your users home directories NFS mounted from a server where a setuid process would be unable to open $HOME/.xauthority? -- -Alan Coopersmith- [EMAIL PROTECTED] Sun Microsystems, Inc. - X Window System Engineering _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
