On Tue, Aug 18, 1998 at 06:27:40PM -0400, Bob Woodside wrote:
> 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.
> 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
Well, no progress. But just yesterday my NT machine BSOD'ed and I had to
restart everything. Again, FvwmCommandS failed to start up via the
InitFunction. I had to start it via my menu entry.
So, coming to think of it, I have _never_ gracefully shutdown and restarted
Fvwm. It has always been due to some emergency, (NT crash, fvwm freeze
during Recapture or Restart, etc). BTW, I am running NT4.0 SP3 with
Netmanage Chameleon UnixLink as my X server.
Leads me to believe that the .FvwmCommandC/S pipes are never cleaned up and
so FvwmCommandS somehow croaks in the InitFunction. Dunno why the menu
entry works though!
Later,
Vikas
--
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 Wed Aug 19 1998 - 06:03:01 BST