On Wed, 19 Aug 1998, Vikas Agnihotri wrote:
> 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
Maybe, you have already told us, but which version of FvwmCommand are you
using?
By a slight chance if it is 1.4 and you are using xdm, version 1.5
should fix it.
I don't think fifos are the problem in your case. They will be overwritten
when a new ones are created, as you run FvwmCommand from menu.
-----------------------------------------------------
Toshi Isogai °ë³ÍøÌÀ
KENTEK Information Systems
isogai_at_kentek.com
--
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 - 10:45:27 BST