Using nohup in cdm-xlaunch for some reason kills the X process after the timeout when launched from tty1, replaced with setsid. No side effects observed, apart from X launching now working.
cdm traps SIGINT for rather obvious reasons. This trap, however, propagates to child processes and cannot be removed by them. Unsetting any traps before calling child processes is a good idea.
I've used these fixes for a while on my own system and figured I might just as well push them here as well.
I mean, I can't be the only one with these issues, can I?
evertiro
commented
12 years ago
Using nohup in cdm-xlaunch for some reason kills the X process after the timeout when launched from tty1, replaced with setsid. No side effects observed, apart from X launching now working.
cdm traps SIGINT for rather obvious reasons. This trap, however, propagates to child processes and cannot be removed by them. Unsetting any traps before calling child processes is a good idea.
I've used these fixes for a while on my own system and figured I might just as well push them here as well.
I mean, I can't be the only one with these issues, can I?