Re: [PATCH xserver] inputthread: leave the main thread's name as-is

2016-10-19 Thread Peter Hutterer
On Tue, Oct 18, 2016 at 12:13:52AM -0700, Jeremy Huddleston Sequoia wrote: > Shouldn't glibc be fixed instead? Why punish the platforms that do it right? at this point I'm not sure yet whether it's glibc or the kernel but I'm betting on the latter. meanwhile, fixing this would be nice so we don't

Re: [PATCH xserver] inputthread: leave the main thread's name as-is

2016-10-18 Thread Jeremy Huddleston Sequoia
Shouldn't glibc be fixed instead? Why punish the platforms that do it right? --Jeremy > On Oct 17, 2016, at 21:13, Peter Hutterer wrote: > > On Linux, setting the main thread's name changes the program name > (/proc/self/comm). Setting it to MainThread breaks scripts that rely on > the command

[PATCH xserver] inputthread: leave the main thread's name as-is

2016-10-17 Thread Peter Hutterer
On Linux, setting the main thread's name changes the program name (/proc/self/comm). Setting it to MainThread breaks scripts that rely on the command name, e.g. ps -C Xorg. Signed-off-by: Peter Hutterer --- os/inputthread.c | 6 -- 1 file changed, 6 deletions(-) diff --git a/os/inputthread.