Bug#843485: mention () vs (()) of filename

2016-11-12 Thread 積丹尼 Dan Jacobson
All I know is "one may have noticed () vs. (())". I don't know how they got there. So I am not the best person to write about it.

Bug#843485: mention () vs (()) of filename

2016-11-12 Thread Ben Hutchings
On Sun, 2016-11-13 at 12:22 +0800, 積丹尼 Dan Jacobson wrote: > BH> The extra parentheses have no special meaning. > > Well please document how they got there at least. As I explained, that program did it: > BH> What the documentation ought to mention is that a thread's name can > BH> be

Bug#843485: mention () vs (()) of filename

2016-11-12 Thread 積丹尼 Dan Jacobson
BH> The extra parentheses have no special meaning. Well please document how they got there at least. BH> What the documentation ought to mention is that a thread's name can BH> be overridden using prctl(PR_SET_NAME, ...). Care to send a patch? I have no kernel knowledge.

Bug#843485: mention () vs (()) of filename

2016-11-12 Thread Ben Hutchings
Control: tag -1 upstream Control: retitle -1 proc.txt does not mention that task names can be overridden On Mon, 2016-11-07 at 07:09 +0800, 積丹尼 Dan Jacobson wrote: > Package: linux-doc-4.8 > Version: 4.8.5-1 > Severity: wishlist > File:

Bug#843485: mention () vs (()) of filename

2016-11-06 Thread 積丹尼 Dan Jacobson
Package: linux-doc-4.8 Version: 4.8.5-1 Severity: wishlist File: /usr/share/doc/linux-doc-4.8/Documentation/filesystems/proc.txt.gz One only sees tcomm filename of the executable But no explanation of () vs (()) $ perl -anwle 'print $F[1]' /proc/[0-9]*/stat|sort -u|head ((sd-pam))