home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ogicse!mintaka.lcs.mit.edu!hal.gnu.ai.mit.edu!wyvern
- From: wyvern@hal.gnu.ai.mit.edu (The Wyvern)
- Newsgroups: comp.os.linux
- Subject: Xlinux8514 and Exit difficulties
- Summary: Temporary fix
- Keywords: shellscript hack
- Message-ID: <1992Sep11.034514.7295@mintaka.lcs.mit.edu>
- Date: 11 Sep 92 03:45:14 GMT
- Article-I.D.: mintaka.1992Sep11.034514.7295
- Sender: news@mintaka.lcs.mit.edu
- Organization: Free Software Foundation
- Lines: 19
-
- I've also been having problems when attempting to exit X8514 when using the
- wm Exit or Quit options. Rather than relying on Ctrl-Alt-Bkspc I replaced
- the 'f.quit' in my twmrc (And did a similar thing for .openwin-menu for olvwm)
- with /bin/sh /home/user1/exitX (or something similar).
- In the exitX file I stuck the simple line
- ps -a | grep twm | grep -v grep | cut -c1-5 | xargs kill
-
- If you're using olvwm or gwm, just change the twm above to your wm name.
- It's possible you may need to mess with the cut settings, but that's always
- done it for me. This tends to produce a nicer exit than C-A-B. I know it's
- crude, but I just thought I'd give people who hate C-A-B a temporary fix.
-
- Incidentally, this lockup doesn't always occur exclusively upon attempted
- exit. I've often been running, say, x11perf, and at times, if I hit Ctrl-C
- in the xterm where it's running, X locks up and I have to do a cold boot.
- Curiously enough the HUP signal seems to produce this effect with surprising
- regularity, which is why I stick with SIGTERM in the exitX line.
-
- Anyway, luck all, and thanks Kevin!
-