sleep 5m; killall fgfs; sleep 1m; killall -9 fgfs; sleep 1m; halt should be executing on a root text console before you start the simulator. I usually find that one of the two killall's will recover the machine. A network login, of course, can do the same thing. However, you generally need to have your filesystem writeable for net services.
> Dave Perry writes: > > I installed the latest development plib tar file and recompiled fgfs. > > No change. > > > > The last 2 lines before the freeze: > > Cannot open file: /usr/local/FlightGear/Scenery/Objects.txt > > Initializing splash screen > > > > The splash screen displays and remains the active window. > > But the systme is frozen. > > > > Don't see what I am doing wrong? > > Your whole system is frozen/locked? That sounds more like a video > driver or hardware problem. Modern system's typically don't let > themselves get locked up, but drivers have kernel level access, and if > you have a hardware problem, *anything* can happen. > > Curt. > -- > Curtis Olson IVLab / HumanFIRST Program FlightGear Project > Twin Cities [EMAIL PROTECTED] [EMAIL PROTECTED] > Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org > > _______________________________________________ > Flightgear-devel mailing list > [EMAIL PROTECTED] > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > > _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
