Re: xinitrc final command with -multiwindow
Phil Betts wrote: There's a registry setting to force programs to quit on shutdown/logoff: http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/rege ntry/34615.mspx?mfr=true True to form, MS only tell half the story in their documentation. They don't say whether the timeouts are honoured before forcing the shutdown, so a shutdown may be immediate, even if an app is prompting you to click OK to cancel the missile launches! You may want to test this first. I was thinking too, a 'nice' future feature may be if Cygwin X would shut down on request, without prompting, if there are no clients? I don't mind, and I actually appreciate the prompt if I have X stuff running and I try to shut down Cygwin X. But if there are no X clients connected, it seems it would be expedient and useful for Cygwin X to go away without a prompt. Jason -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: xinitrc final command with -multiwindow
Jason wrote: I don't know that this helps, but I use the stock startxwin.bat batch file Cygwin/X shipped with. Using that batch file, I am free to close down the Xterm that it starts up, without X dying off. That seems to function by running the X server directly rather than running xinit. Anyone know what I'll miss out on by skipping xinit? (Other than the problem I have with needing to force the xinit process to stick around?) I will seem to lose the ability to run custom stuff in my .xinitrc file, but I think I'd be customizing startxwin.bat/.sh anyway so that wouldn't be an issue I suppose. The only caveate is that this prevents a attendentless shutdown. When you try to shut Windows down, an confirmation will pop up asking if you are sure you want to disconnect all X clients. Even if there are no X clients left running. Windows then sits and waits indefinitely for your answer. You get the same thing with startx. jdb -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
RE: xinitrc final command with -multiwindow
J. David Blackstone wrote on Wednesday, March 21, 2007 2:29 PM:: Jason wrote: I don't know that this helps, but I use the stock startxwin.bat batch file Cygwin/X shipped with. Using that batch file, I am free to close down the Xterm that it starts up, without X dying off. That seems to function by running the X server directly rather than running xinit. Anyone know what I'll miss out on by skipping xinit? (Other than the problem I have with needing to force the xinit process to stick around?) I will seem to lose the ability to run custom stuff in my .xinitrc file, but I think I'd be customizing startxwin.bat/.sh anyway so that wouldn't be an issue I suppose. That's what I do. Just convert anything you need from the xinitrc to run in the .bat file, or put them in a separate script and run it via bash. Make sure you don't change startxwin.bat itself, but work on a copy instead. If you change the original, the next update will overwrite your changes (you might detect the voice of bitter experience here). The only caveate is that this prevents a attendentless shutdown. When you try to shut Windows down, an confirmation will pop up asking if you are sure you want to disconnect all X clients. Even if there are no X clients left running. Windows then sits and waits indefinitely for your answer. You get the same thing with startx. There's a registry setting to force programs to quit on shutdown/logoff: http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/rege ntry/34615.mspx?mfr=true True to form, MS only tell half the story in their documentation. They don't say whether the timeouts are honoured before forcing the shutdown, so a shutdown may be immediate, even if an app is prompting you to click OK to cancel the missile launches! You may want to test this first. Phil -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: xinitrc final command with -multiwindow
http://cygwin.com/acronyms/#PCYMTWLL. Thanks. On Wed, 21 Mar 2007, J. David Blackstone wrote: Since X exits when the xinitrc process terminates, xinitrc needs to finish by starting a program that will run for the duration of my X session. Traditionally this is a window manager, but with -multiwindow a window manager is already running. So with -multiwindow the usual course of action is to exec an xterm. But when that xterm exits, so does X. Unfortunately I'm very prone to getting that magic xterm mixed up with all my others, and shutting down my whole session without intending to. Also, I don't want that xterm because I have my XWinrc set up to run every command that I want to run (mostly a series of xterms that ssh to other servers, as well as a local xterm, of course). I just moved to a new machine at work, and managed to back up everything I needed except my xinitrc. Somehow I had figured out what to exec at the end of xinitrc to avoid having that magic xterm, but I can't remember what I did! I think I found it on a Cygwin mailing list, probably three years ago. But tonight I can find no reference to it at all. I know that for a time I just ended xinitrc with a loop that did a sleep 60 or something over and over again. But that was awkward and had problems. At one point I started up xclock or something. Does anyone know what the standard suggestion for the last command of xinitrc is when you cannot run a window run a window manager and you do not want to run an xterm or anything else that clutters up the task bar? It'd be nice if sleep just had an option to sleep indefinitely until killed (I exit from the XWinrc menu), but that doesn't seem to be available. sleep 1d should do it -- I doubt your computer will last that long. :-) Or you could use the -noreset X option. HTH, Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] | [EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_Igor Peshansky, Ph.D. (name changed!) |,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Freedom is just another word for nothing left to lose... -- Janis Joplin -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
xinitrc final command with -multiwindow
Since X exits when the xinitrc process terminates, xinitrc needs to finish by starting a program that will run for the duration of my X session. Traditionally this is a window manager, but with -multiwindow a window manager is already running. So with -multiwindow the usual course of action is to exec an xterm. But when that xterm exits, so does X. Unfortunately I'm very prone to getting that magic xterm mixed up with all my others, and shutting down my whole session without intending to. Also, I don't want that xterm because I have my XWinrc set up to run every command that I want to run (mostly a series of xterms that ssh to other servers, as well as a local xterm, of course). I just moved to a new machine at work, and managed to back up everything I needed except my xinitrc. Somehow I had figured out what to exec at the end of xinitrc to avoid having that magic xterm, but I can't remember what I did! I think I found it on a Cygwin mailing list, probably three years ago. But tonight I can find no reference to it at all. I know that for a time I just ended xinitrc with a loop that did a sleep 60 or something over and over again. But that was awkward and had problems. At one point I started up xclock or something. Does anyone know what the standard suggestion for the last command of xinitrc is when you cannot run a window run a window manager and you do not want to run an xterm or anything else that clutters up the task bar? It'd be nice if sleep just had an option to sleep indefinitely until killed (I exit from the XWinrc menu), but that doesn't seem to be available. jdb -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: xinitrc final command with -multiwindow
J. David Blackstone wrote: snip Does anyone know what the standard suggestion for the last command of xinitrc is when you cannot run a window run a window manager and you do not want to run an xterm or anything else that clutters up the task bar? It'd be nice if sleep just had an option to sleep indefinitely until killed (I exit from the XWinrc menu), but that doesn't seem to be available. I don't know that this helps, but I use the stock startxwin.bat batch file Cygwin/X shipped with. Using that batch file, I am free to close down the Xterm that it starts up, without X dying off. The only caveate is that this prevents a attendentless shutdown. When you try to shut Windows down, an confirmation will pop up asking if you are sure you want to disconnect all X clients. Even if there are no X clients left running. Windows then sits and waits indefinitely for your answer. Jason -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
