hbergh@oracle.nl (Herbert van den Bergh) (09/14/90)
In article <IVAN%NEPJT.90Sep13133133@nepjt.ncsuvx.ncsu.edu> ivan%nepjt@ncsuvx.ncsu.edu (Ivan Maldonado) writes: >Under the absence of a "screen saver" utility, I find myself >doing a "ps -a" and a "kill PID" to kill "X" from the console >all the time. It has been mentioned here before: Typing Ctrl-Alt-Backspace on the graphics screen keyboard will stop the X server. -- Herbert van den Bergh, ORACLE Europe hbergh@oracle.nl, hbergh@oracle.com Rijnzathe 6, NL-3454 PV De Meern uunet!mcsun!orcenl!hbergh Phone: +31-3406-94211
ron@woan (Ronald S. Woan) (09/15/90)
In article <957@nlsun1.oracle.nl>, hbergh@oracle.nl (Herbert van den Bergh) writes: In article <IVAN%NEPJT.90Sep13133133@nepjt.ncsuvx.ncsu.edu> ivan%nepjt@ncsuvx.ncsu.edu (Ivan Maldonado) writes: >Under the absence of a "screen saver" utility, I find myself >doing a "ps -a" and a "kill PID" to kill "X" from the console >all the time. Herbert> It has been mentioned here before: Herbert> Typing Ctrl-Alt-Backspace on the graphics screen keyboard will Herbert> stop the X server. Then again, a lot of us disable this "feature" when invoking X to make using xlock more secure... ctrl-alt-bspace doesn't really seem any more elegant than a kill... Ron +-----All Views Expressed Are My Own And Are Not Necessarily Shared By------+ +------------------------------My Employer----------------------------------+ + Ronald S. Woan woan@peyote.cactus.org or woan@austin.iinus1.ibm.com + + other email addresses Prodigy: XTCR74A Compuserve: 73530,2537 +
rudy@chukran.austin.ibm.com (09/15/90)
I just kill mwm with the menu popdown provided. I startup X with "open xinit". the last thing in xinitrc is "exec mwm", therefore mwm becomes the process group leader for the virtual terminal. When mwm exits, all her children get a SIGHUP, including X. No nasty messages about server killed either. ********************************************************************* Rudy Chukran | EMAIL: IBM AIX Porting Center | RSCS: CHUKRAN at AUSTIN 11400 Burnet Rd. | AWDnet: rudy@chukran.austin.ibm.com Internal ZIP 2830 | internet: chukran@austin.iinus1.ibm.com Austin, Texas 78758 | Voice: 512-838-4674 Tieline: 678-4674 *********************************************************************
ivan%nepjt@ncsuvx.ncsu.edu (Ivan Maldonado) (09/16/90)
In article <3511@awdprime.UUCP> ron@woan (Ronald S. Woan) writes: > In article <957@nlsun1.oracle.nl>, hbergh@oracle.nl (Herbert van den > Bergh) writes: > In article <IVAN%NEPJT.90Sep13133133@nepjt.ncsuvx.ncsu.edu> > ivan%nepjt@ncsuvx.ncsu.edu (Ivan Maldonado) writes: > >Under the absence of a "screen saver" utility, I find myself > >doing a "ps -a" and a "kill PID" to kill "X" from the console > >all the time. > Herbert> It has been mentioned here before: > Herbert> Typing Ctrl-Alt-Backspace on the graphics screen keyboard will > Herbert> stop the X server. > Then again, a lot of us disable this "feature" when invoking X to make > using xlock more secure... ctrl-alt-bspace doesn't really seem any > more elegant than a kill... > Ron I sort of agree with Ron. When xclock and/or any other X window is active at the time you do a Ctrl-Alt-Backspace, you end up getting a "broken pipe" message. I think a "quit X" option was left out from the same menu one uses to open a new window. Then again, that's me thinking.... oh no!! Thank you all for your replies. -Ivan -- ------------------------------------------------------------------------------ | Guillermo Ivan Maldonado | Internet: ivan%nepjt@ncsuvx.ncsu.edu | | Department of Nuclear Engineering | BITNET : maldonado@ncsune | | North Carolina State University |---------------------------------------- | NCSU Box # 7909 | ... que viva Quito ! | | Raleigh. NC 27606-7909 | ... que viva el ECUADOR !! | ------------------------------------------------------------------------------
ivan%nefx4@ncsuvx.ncsu.edu (Ivan Maldonado) (09/16/90)
On 14 Sep 90 22:02:08 GMT, rudy@chukran.austin.ibm.com said: > I just kill mwm with the menu popdown provided. > I startup X with "open xinit". > the last thing in xinitrc is "exec mwm", therefore mwm becomes the > process group > leader for the virtual terminal. When mwm exits, all her children get > a SIGHUP, > including X. No nasty messages about server killed either. Thank you, this works much more neatly. One thing, however, the menu popdown I get (the same one used to open a new window) has a "restart mwm" option, and not a "kill mwm". So I end up using "ps -a" and then "kill PID(mwm)". No "broken pipes" just like you said. -Ivan -- ------------------------------------------------------------------------------ | Guillermo Ivan Maldonado | Internet: ivan%nefx4@ncsuvx.ncsu.edu | | Department of Nuclear Engineering | BITNET : maldonado@ncsune | | North Carolina State University |---------------------------------------- | NCSU Box # 7909 | ... que viva Quito ! | | Raleigh. NC 27606-7909 | ... que viva el ECUADOR !! | ------------------------------------------------------------------------------
m-hirano@sra.co.jp (09/17/90)
In article <3511@awdprime.UUCP> ron@woan (Ronald S. Woan) writes: >>:In article <957@nlsun1.oracle.nl>, hbergh@oracle.nl (Herbert van den >>:Bergh) writes: >>:In article <IVAN%NEPJT.90Sep13133133@nepjt.ncsuvx.ncsu.edu> >>:ivan%nepjt@ncsuvx.ncsu.edu (Ivan Maldonado) writes: >>:>Under the absence of a "screen saver" utility, I find myself >>:>doing a "ps -a" and a "kill PID" to kill "X" from the console >>:>all the time. >>:Herbert> It has been mentioned here before: >>:Herbert> Typing Ctrl-Alt-Backspace on the graphics screen keyboard will >>:Herbert> stop the X server. >>: >>:Then again, a lot of us disable this "feature" when invoking X to make >>:using xlock more secure... ctrl-alt-bspace doesn't really seem any >>:more elegant than a kill... I think this is the first time posting to this newsgroup from Japan :-) . Even if My english is funny, I hope you can understand what I want to say :-) I always think that "Ctrl-Alt-Backspace" is NOT a elegant way to kill X server. So, I ported "xinit" included in X11R4 MIT distribution and replaced IBM's shell script xinit to this. Then I wrote a ".xserverrc" in my home directory like this X -n :0 -T -f 70 -c 60 -a 2 -fn rom17 and at the end of .xinitrc, I do "exec xterm". So I exit from xterm invoked by .xinitrc, my X server is going to kill just like another machine's X server. Thank you for reading. from Japan with LOVE... Motonori "Heita" Hirano Software Research Associates, Inc., Japan E-mail: m-hirano@sra.co.jp
rudy@chukran (09/18/90)
The default mwmrc that comes with the system removes the "quit mwm" line. "Quit Window Manager" f.quit_mwm ********************************************************************* Rudy Chukran | EMAIL: IBM AIX Porting Center | RSCS: CHUKRAN at AUSTIN 11400 Burnet Rd. | AWDnet: rudy@chukran.austin.ibm.com Internal ZIP 2830 | internet: chukran@austin.iinus1.ibm.com Austin, Texas 78758 | Voice: 512-838-4674 Tieline: 678-4674 *********************************************************************
ron@woan (Ronald S. Woan) (09/18/90)
In article <M-HIRANO.90Sep17163624@ext106.sra.co.jp>, m-hirano@sra.co.jp writes: Motonori> So, I ported "xinit" included in X11R4 MIT distribution and Motonori> replaced IBM's shell script xinit to this. Motonori> Then I wrote a ".xserverrc" in my home directory like this Forgive my ignorance, but what does the X11R4 xinit program feature? I always thought that it was basically like the supplied shell script, in that it invokes a user's ~/.xinitrc when found... Motonori> X -n :0 -T -f 70 -c 60 -a 2 -fn rom17 Motonori> and at the end of .xinitrc, I do "exec xterm". So I exit Motonori> from xterm invoked by .xinitrc, my X server is going to kill Motonori> just like another machine's X server. The "exec window manager" may have been just a touch nicer for most people, except the "exec xterm" does allow you to swap out window managers without ending the X session. Ron +-----All Views Expressed Are My Own And Are Not Necessarily Shared By------+ +------------------------------My Employer----------------------------------+ + Ronald S. Woan woan@peyote.cactus.org or woan@austin.iinus1.ibm.com + + other email addresses Prodigy: XTCR74A Compuserve: 73530,2537 +
peter@dbaccess.com (Peter A. Castro) (09/19/90)
in article <IVAN%NEFX4.90Sep15181026@nefx4.ncsuvx.ncsu.edu>, ivan%nefx4@ncsuvx.ncsu.edu (Ivan Maldonado) says: > In-reply-to: rudy@chukran.austin.ibm.com's message of 14 Sep 90 22:02:08 GMT > > > On 14 Sep 90 22:02:08 GMT, > rudy@chukran.austin.ibm.com said: > >> I just kill mwm with the menu popdown provided. >> I startup X with "open xinit". >> the last thing in xinitrc is "exec mwm", therefore mwm becomes the >> process group >> leader for the virtual terminal. When mwm exits, all her children get >> a SIGHUP, >> including X. No nasty messages about server killed either. > > Thank you, this works much more neatly. One thing, however, > the menu popdown I get (the same one used to open a new window) > has a "restart mwm" option, and not a "kill mwm". So I end up > using "ps -a" and then "kill PID(mwm)". No "broken pipes" just > like you said. There should be another menu item called "Exit MWM" (at the bottom, just after the Restart item). This item does the kill of the mwm for you and cleans up things. You should have a .mwmrc file in your home directory. If not, you can get a copy of the system one. It should be in /usr/lib/X11/system.mwmrc. Here is an example of the RootMenu with the Exit MWM item: # Root Menu Description Menu RootMenu { "Root Menu" f.title no-label f.separator "New Window" f.exec "aixterm &" "Shuffle Up" f.circle_up "Shuffle Down" f.circle_down "Refresh" f.refresh no-label f.separator "InfoExplorer" f.exec "info -g" "xclock" f.menu Xclocks "xbiff" f.exec "xbiff &" no-label f.separator "Backgrounds.." f.menu Backgrounds no-label f.separator "Restart..." f.restart "Exit MWM" f.quit_mwm } Just like the Restart prompts you for restarting the MWM, the Exit MWM item prompts you to quit the mwm (Yes or No? ). > > -Ivan > > > -- > ------------------------------------------------------------------------------ > | Guillermo Ivan Maldonado | Internet: ivan%nefx4@ncsuvx.ncsu.edu | > | Department of Nuclear Engineering | BITNET : maldonado@ncsune | > | North Carolina State University |---------------------------------------- > | NCSU Box # 7909 | ... que viva Quito ! | > | Raleigh. NC 27606-7909 | ... que viva el ECUADOR !! | > ------------------------------------------------------------------------------ -- Peter A. Castro INTERNET: peter@dbaccess.com // //| c/o DB/Access Inc. UUCP: {uunet,mips}!troi!peter // //|| 2900 Gordon Avenue, Suite 101 FAX: (408) 735-0328 \\ // //-||- Santa Clara, CA 95051-0718 TEL: (408) 735-7545 \// // ||
m-hirano@sra.co.jp (09/19/90)
In article <3560@awdprime.UUCP> ron@woan (Ronald S. Woan) writes:
Ron >>Forgive my ignorance, but what does the X11R4 xinit program feature? I
Ron >>always thought that it was basically like the supplied shell script,
Ron >>in that it invokes a user's ~/.xinitrc when found...
make sense !
program "xinit" invokes X and ~/.xinitrc. There is no problem
and no difference between X11R4 and X11R3.
Why I had to kill X by "Ctrl-Alt-Backspace" is " AIXwindow's
xinit invokes ~/.xinitrc with "&". ".
So, even if I invoke "exec XXX" at the end of ~/.xinitrc and
exit from XXX, I can't kill X.
I don't want to modify "/usr/lpp/X11/bin/xinit" ,
I use X11's xinit :-)
Motonori "Heita" Hirano
Software Research Associates, Inc., Japan
E-mail: m-hirano@sra.co.jp