From: George Anzinger <george@mvista.com>
To: Chris Swiedler <chris.swiedler@sevista.com>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: getting a process name from task struct
Date: Thu, 09 Nov 2000 10:03:16 -0800 [thread overview]
Message-ID: <3A0AE6E4.103C13F5@mvista.com> (raw)
In-Reply-To: <NDBBIAJKLMMHOGKNMGFNCEEHCPAA.chris.swiedler@sevista.com>
Chris Swiedler wrote:
>
> Is it possible to get a process's name / full execution path (from
> kernelspace) given only a task struct? I can't find any pointers to this
> information in the task struct, and I don't know where else it might be. ps
> seems to be able to get the process name, but that's from userspace.
> Apologies in advance if this is a stupid question.
>
> chris
>
Try the "comm" member of task_struct. (Clear name, right?)
George
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-11-09 18:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-09 17:45 getting a process name from task struct Chris Swiedler
2000-11-09 18:03 ` George Anzinger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A0AE6E4.103C13F5@mvista.com \
--to=george@mvista.com \
--cc=chris.swiedler@sevista.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox