AHA! That's it.
Suggestion for a future update: FvwmCommandS and FvwmCommand
might check whether the home directory is NFS-mounted, and if
so use something like /tmp/$DISPLAY/.FvwmCommand as the default
FIFO set. (I try to avoid global places like /tmp/FvwmCommand,
in case there might be another FVWM running on the same system,
e.g. for an Xterminal.)
In the meantime, it might be worth adding this tidbit to the
FvwmCommand manpage or the FAQ.
> Is the location of your pipes by any chance on NFS. Pipes don't work
> on NFS. If you do FvwmCommandS /tmp/FvwmCommand
> then use FvwmCommand /tmp/FvwmCommand
>
> Brad
>
> On Fri, Nov 17, 2000 at 02:15:18PM -0500, David S. Goldberg wrote:
> > > $ ls -l .FvwmCommand*
> > > crw------- 1 phutchis phutchis 255, 255 Nov 16 19:03 .FvwmCommandC
> > > crw------- 1 phutchis phutchis 255, 255 Nov 16 19:03 .FvwmCommandM
> >
> > Those don't look like FIFO's to me. On all my "normal" UNIX systems,
> > including RH6.2, FIFO's are listed with a `p' in the first column.
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Fri Nov 17 2000 - 14:15:56 GMT