On 18-Aug-98 edtawfal_at_value.net wrote:
> When FvwmCommandS is started it exits or dies with the message:
> "FvwmCommandS: dead pipe"
> I assume that is bad.
That is bad. (That's what FvwmCommandS says when you kill it
normally with KillModule, though.)
I have no idea what's going on here. I've never had it fail to
start up, so any suggestions I make are pure guesswork.
1) Was FvwmCommandS compiled at the same time as the main part
of Fvwm - same compiler release, libs, etc.?
2) Someone else recently reported that he couldn't get FvwmCommandS
to start properly from his InitFunction (Vikas, are you following this one,
and have you made any progress?) If that's how you're starting it, try
putting it into a menu and invoke it after Fvwm gets started up. If this
makes a difference, at least we have a clue about where to look. I'm not
sure what we'd be looking for - some kind of timing quirk, I guess - I can't
make it fail this way, either.
> Using FvwmCommand results in an error of:
> "No such file or directory FvwmCommand error in opening message fifo"
> This error is given with ANY command I try.
This is the normal response from FvwmCommand if FvwmCommandS is
not active.
> PS: this is version Ver. 1.5 of FvwmCommand, ver. 2.0.46 of Fvwm2, libc6
This is curious - where did your Fvwm come from? The FvwmCommand in
my copy of Fvwm 2.0.46 identifies itself as version 1.4. Unless that's a
typo, there may be something fishy here.
--
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 Aug 18 1998 - 17:42:23 BST