Difference between revisions of "Talk:Xinit"

From ArchWiki
Jump to: navigation, search
(bg)
(Backgrounding: typo)
Line 9: Line 9:
 
The article points out that any process (e.g. programs and daemons) preceding the 'exec WM/DE' statement should be backgrounded. This sounds logical in order to execute all of the desired statements (included the WM/DM launcher), without waiting for a process to exit. Looking at the file examples (some provided by myself), I noticed that 'xrdb ...' is not backgrounded. This made me test my own [https://github.com/roygbiiv/dotfiles/blob/master/.xinitrc config], without backgrounding anything except the 'xscreensaver' daemon statement, and the results are the same - only I don't have a lot of backgrounded processes when using 'ps -a'. This matter confuses me a little so, my question is: are there any general rule on what processes should be backgrounded in .xinitrc? Starting daemons is one example of processes that should be backgrounded. --[[User:Roygbiv|Roygbiv]] 16:55, 28 August 2011 (EDT)
 
The article points out that any process (e.g. programs and daemons) preceding the 'exec WM/DE' statement should be backgrounded. This sounds logical in order to execute all of the desired statements (included the WM/DM launcher), without waiting for a process to exit. Looking at the file examples (some provided by myself), I noticed that 'xrdb ...' is not backgrounded. This made me test my own [https://github.com/roygbiiv/dotfiles/blob/master/.xinitrc config], without backgrounding anything except the 'xscreensaver' daemon statement, and the results are the same - only I don't have a lot of backgrounded processes when using 'ps -a'. This matter confuses me a little so, my question is: are there any general rule on what processes should be backgrounded in .xinitrc? Starting daemons is one example of processes that should be backgrounded. --[[User:Roygbiv|Roygbiv]] 16:55, 28 August 2011 (EDT)
 
:I'm using [https://aur.archlinux.org/packages.php?O=0&K=urxvtcd&do_Search=Go urxvtcd] and it doesn't have to be backgrounded in order for dwm to start. If I use urxvt instead, dwm won't start unless I background urxvt or it starts only after I exit urxvt. -- [[User:Karol|Karol]] 17:13, 28 August 2011 (EDT)
 
:I'm using [https://aur.archlinux.org/packages.php?O=0&K=urxvtcd&do_Search=Go urxvtcd] and it doesn't have to be backgrounded in order for dwm to start. If I use urxvt instead, dwm won't start unless I background urxvt or it starts only after I exit urxvt. -- [[User:Karol|Karol]] 17:13, 28 August 2011 (EDT)
::Ok. So it isn't necessarily so that all daemon processes must be backgrounded. Looking at other processes, it's not clear to me what to do. In the this talk page [[https://wiki.archlinux.org/index.php/Talk:X_resources]] there was an issue with backgrounding xrdb statements. and the solution was not backgrounding it. I guess maybe there isn't a general rule for all processes, because it depends how the different processes behave, but backgrounding in most cases is more generally adviced to not screw up the xinit process? I don't know here. -- [[User:Roygbiv|Roygbiv]] 02:04, 29 August 2011 (EDT)
+
::Ok. So it isn't necessarily so that all daemon processes must be backgrounded. Looking at other processes, it's not clear to me what to do. In the this talk page:[https://wiki.archlinux.org/index.php/Talk:X_resources xresources] there was an issue with backgrounding xrdb statements. And the solution was not backgrounding it. I guess maybe there isn't a general rule for all processes, because it depends how the different processes behave, but it seems backgrounding in most cases is more generally adviced to not screw up the xinit process. I don't know here. -- [[User:Roygbiv|Roygbiv]] 02:04, 29 August 2011 (EDT)

Revision as of 06:06, 29 August 2011

Great article. About time .xinitrc got its own wiki entry. Thanks for your contribution. Misfit138 14:02, 29 September 2008 (EDT)

Thanks :) Chochem 04:44, 2 October 2008 (EDT)


Maybe we could have a section on ck-launch-session? I don't know enough to be useful. Daenyth 12:52, 7 February 2010 (EST)

Backgrounding

The article points out that any process (e.g. programs and daemons) preceding the 'exec WM/DE' statement should be backgrounded. This sounds logical in order to execute all of the desired statements (included the WM/DM launcher), without waiting for a process to exit. Looking at the file examples (some provided by myself), I noticed that 'xrdb ...' is not backgrounded. This made me test my own config, without backgrounding anything except the 'xscreensaver' daemon statement, and the results are the same - only I don't have a lot of backgrounded processes when using 'ps -a'. This matter confuses me a little so, my question is: are there any general rule on what processes should be backgrounded in .xinitrc? Starting daemons is one example of processes that should be backgrounded. --Roygbiv 16:55, 28 August 2011 (EDT)

I'm using urxvtcd and it doesn't have to be backgrounded in order for dwm to start. If I use urxvt instead, dwm won't start unless I background urxvt or it starts only after I exit urxvt. -- Karol 17:13, 28 August 2011 (EDT)
Ok. So it isn't necessarily so that all daemon processes must be backgrounded. Looking at other processes, it's not clear to me what to do. In the this talk page:xresources there was an issue with backgrounding xrdb statements. And the solution was not backgrounding it. I guess maybe there isn't a general rule for all processes, because it depends how the different processes behave, but it seems backgrounding in most cases is more generally adviced to not screw up the xinit process. I don't know here. -- Roygbiv 02:04, 29 August 2011 (EDT)