On Thu, 20 Mar 1997, Bill Randle wrote:
> I'm running fvwm2 on a Solaris 2.5 system (SS-20) and haven't experienced
> any problems with xlock. I checked my path, though, and noticed that I'm
> picking up the X11R5 version of xlock (which we put in /usr/X11/bin)
> rather than Sun's version:
>
> -rwxr-xr-x 1 bin 78952 Jun 8 1994 /usr/X11/bin/xlock
> -rwsrwxr-x 1 root 94484 Oct 2 1995 /usr/openwin/bin/xlock
>
> Note that the two are quite different is size and that the Sun version is
> suid root. I have no idea what the actual differences are. The source
> for xlock comes with the standard X11 distribution which can be found at
> ftp.x.org, amoung other places.
Thanx for your reply, but my sysadmin and I figured out the problem. Well,
he did, I was just watching :) In any case, it seems that a required env.
variable is not being set during xdm startup... the env name is LOGNAME
... Once this is set properly, it will work just fine... Thanx!
-peace
-----BEGIN GEEK CODE BLOCK-----
GAT d- s:+ !a C+(+++) UI/L/S/B++(+++) P>+ L+(++) E---- W+++ N+ o? K?
w++++ O--- M-- V PS+++_at_ PE Y-- PGP+ t++ 5 X++ R- tv+ b DI++ D+ G e>*
h*(!) r- y*(+)
------END GEEK CODE BLOCK------
"Life is when you shake it" -- me
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Thu Mar 20 1997 - 10:58:08 GMT