Da Zheng, le Wed 17 Mar 2010 18:02:42 +0800, a écrit : > On 10-3-17 下午5:48, Samuel Thibault wrote: > >>> For the record, here are the initial tasks and their pid: > >>> > >>> task 0 pid 2: gnumach > >>> task 1 pid 3: ext2fs > >>> task 2 pid 4: exec > >>> task 3 pid 1: init > >>> task 4 pid 0: proc > >>> task 5 pid 5: auth > >>> task 6 pid 6: /bin/bash > >> OK, so the task that triggers the warning is exec during login. How do you > >> get > >> the mapping between task ID and pid? > > > > Well, task 0, 1, 2, 3, 4 and 5 are clearly gnumach, ext2fs, exec, init, > > proc and auth, just read the usual boot log :) Then just run ps to know > > which PID they have. > But kdb doesn't display pid, does it?
It does not, it's just a reminder. > After I get pid from ps, how do I map it to task ID in kdb? You can't, only the proc server knows that. But for the initial tasks, you know in which order they get started, and thus their task number. Samuel
