From: KOSAKI Motohiro <kosaki.motohiro@gmail.com>
To: matthieu castet <castet.matthieu@free.fr>
Cc: linux-kernel@vger.kernel.org,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Timo Sirainen <tss@iki.fi>, Bryan Donlan <bdonlan@gmail.com>,
Ulrich Drepper <drepper@redhat.com>
Subject: Re: [PATCH] Added PR_SET_PROCTITLE_AREA option for prctl()
Date: Mon, 5 Oct 2009 00:10:04 +0900 [thread overview]
Message-ID: <2f11576a0910040810g1cb5bb26l1c522a4f51f843bb@mail.gmail.com> (raw)
In-Reply-To: <loom.20091003T131407-865@post.gmane.org>
>> PR_SET_PROCTITLE_AREA updates mm_struct->arg_start and arg_end to the
>> given pointers, which makes it possible for user space to implement
>> setproctitle(3) cleanly.
>>
>>
> Why can't you use PR_SET_NAME ?
example:
% ps -ef |grep sendmail
root 2444 1 0 Oct04 ? 00:00:00 sendmail: accepting connections
smmsp 2454 1 0 Oct04 ? 00:00:00 sendmail: Queue
runner@01:00:00 for /var/spool/clientmqueue
kosaki 3927 2907 0 00:02 pts/1 00:00:00 grep sendmail
Almost setproctitle() heavy user (e.g. sendmail, openssh and some bsd
style daemon programs) use long string rather than 16.
> And with PR_SET_NAME, you can a name per thread, which you can't do by changing
> arg[0] name (it should be shared across all thread).
>
> Matthieu
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
prev parent reply other threads:[~2009-10-04 15:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 21:23 Timo Sirainen
2009-10-03 2:01 ` Bryan Donlan
2009-10-03 2:47 ` Timo Sirainen
2009-10-03 2:59 ` Bryan Donlan
2009-10-03 3:21 ` Timo Sirainen
2009-10-04 14:44 ` KOSAKI Motohiro
2009-10-04 18:05 ` Bryan Donlan
2009-10-05 0:55 ` KOSAKI Motohiro
2009-10-05 1:38 ` KOSAKI Motohiro
2009-10-05 1:44 ` Bryan Donlan
2009-10-05 1:59 ` KOSAKI Motohiro
2009-10-05 2:21 ` Bryan Donlan
2009-10-05 2:24 ` KOSAKI Motohiro
2009-10-05 2:48 ` KOSAKI Motohiro
2009-10-05 3:22 ` Bryan Donlan
2009-10-05 3:29 ` KOSAKI Motohiro
2009-10-05 3:39 ` Bryan Donlan
2009-10-05 7:18 ` KOSAKI Motohiro
2009-10-05 22:56 ` Timo Sirainen
2009-10-03 11:18 ` matthieu castet
2009-10-04 15:10 ` KOSAKI Motohiro [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=2f11576a0910040810g1cb5bb26l1c522a4f51f843bb@mail.gmail.com \
--to=kosaki.motohiro@gmail.com \
--cc=bdonlan@gmail.com \
--cc=castet.matthieu@free.fr \
--cc=drepper@redhat.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tss@iki.fi \
/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
all inboxes | Powered by JetHome®