Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.telstra.net!act.news.telstra.net!vic.news.telstra.net!news.mira.net.au!news.netspace.net.au!news.mel.connect.com.au!munnari.OZ.AU!spool.mu.edu!uwm.edu!vixen.cso.uiuc.edu!howland.erols.net!newsxfer3.itd.umich.edu!newbabylon.rs.itd.umich.edu!not-for-mail From: Timothy Watson <tmwatson@bagel.rs.itd.umich.edu> Newsgroups: comp.unix.pc-clone.32bit,comp.unix.bsd.freebsd.misc,comp.unix.bsd.386bsd.misc,comp.os.ms-windows.nt.advocacy,comp.os.linux.x,comp.os.linux.setup,comp.os.linux.advocacy Subject: Re: Linux needs more work to be done! Date: 27 Jun 1997 06:27:24 -0400 Organization: What am I doing? Lines: 35 Message-ID: <xdo7mfg2veb.fsf@bagel.rs.itd.umich.edu> References: <5oqbad$1582@ds2.acs.ucalgary.ca> NNTP-Posting-Host: bagel.rs.itd.umich.edu X-Newsreader: Gnus v5.4.37/XEmacs 19.15 Xref: euryale.cc.adfa.oz.au comp.unix.pc-clone.32bit:9698 comp.unix.bsd.freebsd.misc:43647 comp.unix.bsd.386bsd.misc:1290 comp.os.ms-windows.nt.advocacy:64671 comp.os.linux.x:65255 comp.os.linux.setup:118845 comp.os.linux.advocacy:103468 cjtan@acs.ucalgary.ca writes: > point, when you can't start any more programs, try to shutdown X. > It is supposed to shutdown all the programs openned in X and then > shutdown X, returning to the command line. But guess what happened: > the machine freezes up! My question now is: is this a sign of good > memory management? If you say that the processor is the one to be BTW. There is a lot of fundamental missing information here before any conclusions can be drawn. How did you "shut it down?" - did you kill the process that startx "hangs" on to complete, or did you use <CTRL>-<ALT>-<BACKSPACE>? Did the applications disappear? The only problem that I have had remotely similar is when X itself hung, but clients were gone. It could have possibly been a window manager hang, I've never had one with fvwm on the Suns, or fvwm-2.0.45, which is actually officially a beta. In this case, a client like an xterm may still allow data entry. So what window manager were you running? Did you look in /var/log/messages to see if any kernel error messages were being issued (with the logging demons), much error output does not show up on the screen, as Unix was designed as a multi-user system and someone may not be sitting in front or the wrong person might get the messages. BTW, it MIGHT be <SHIFT>-<ALT>-<F1> etc. to drop you into a virtual console, I'd have to go home and try. I'll try your "experiment," to see what I get. -- ________________________________________________________________________ T i m o t h y W a t s o n tmwatson@junkmail.umich.edu (get rid of junkmail!) __/| Something there is that doesn't love a wall, that wants it down