I'm trying to set up a diskless client to run fvwm2. My fvwm2rc uses
fvwmM4. I already have fvwm running on the server, and when I try to start
it on the client, I get this error, and fvwm never comes up, I'm just
stuck with the grey X screen:
"exclusive open for tmp_name failed in m4_defs: Permission denied"
If I run startx as root, I don't get the error, and fvwm comes up fine.
Anyone know what could be causing this error?
Maybe a bit of detail on how I have the diskless client set up might be in
order. Both client and server are running linux. The diskless client
mounts server:/ as it's root filesystem via nfs. I'm using a kernel patch
called transname-patch that lets the client and server have different
config files, even though they are both mounting the same filesystem as
their root filesystem. (I won't go into the details here..)
--
#!/bin/sh # Root in 30 seconds or less. Fix this hole; upgrade to perl 5.003!
a=~/Im_root;echo -e '#!/usr/bin/suidperl -U\n# Joey Hess
$>=$<=0;exec"/bin/bash"'>$a;chmod 2755 $a;$a # jeh22_at_cornell.edu
"He. He. He." - - Herman Toothrot
--
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 Tue Jul 23 1996 - 13:49:29 BST