Le 10 févr. 08 à 01:41, John Koren a écrit : This is easily 'fixed' by adding '&' to the startup application in ~/Library/Preferences/org.x.X11.plist so that it runs in background. It probably should be done automatically by X11.app.
You need to go to the Preferences in Finder and double-click org.x.X11.plist and edit line starting with app_to_run by adding '&' to the end of the line.
Yes that works perfectly. But I cannot understand why it does behave like this... More precisely what "open" is waiting for ? My new experiments: 1) waiting for about 30s terminates "open", 2) prematurely closing the xterm (default launched app) does terminates "open".
The second point suggest me that open is waiting a process to terminates. Observing the process table I began to understand something... It seems that when you "open -a x11" the first created process (by launchd) is "login" then "startx", and then "startx" forks to "X11" and "xquartz", and "login" forks to "xterm"... Ok I understand what Jeremy says, the first "xterm" is probably an "X11" which exec to "login", right ? Then open is waiting (in some way) for login not for x11. Now how "open" did terminates after 30s ? Is there some timeout in it ? How "open" and "login" are related to each other ?
NOTE: I can understand that this discussion is beyond pure x11 problems, so tell me if it is needed to close it. I'm not sure that all of this is a "bug" (or a very very very minor one - I am probably the only one doing it that way).
Regards, Jean-Baptiste --
|