From: "Stone, Joshua I" <joshua.i.stone@intel.com>
To: "Frank Ch. Eigler" <fche@elastic.org>,
"David Smith" <dsmith@redhat.com>
Cc: <systemtap@sources.redhat.com>
Subject: RE: precompiled probing scenarios
Date: Fri, 20 Oct 2006 20:51:00 -0000 [thread overview]
Message-ID: <C56DB814FAA30B418C75310AC4BB279DCC4312@scsmsx413.amr.corp.intel.com> (raw)
On Friday, October 20, 2006 1:13 PM, Frank Ch. Eigler wrote:
> Hi -
>
> dsmith wrote:
>> [...]
>> I don't hash the getuid(), since:
>> - by default your cache is stored in your home directory
>> - who you are doesn't change the pass 2-4 output
>
> That's all true. One possible reason for including getuid() anyway is
> so that two different sudo-empowered people can run the same script at
> the same time without one having to disable his cache.
Also, uid isn't always in sync with $HOME. Besides people doing weird
things tweaking it, a simple example is that sudo may or may not change
$HOME to ~root.
Josh
next reply other threads:[~2006-10-20 20:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 20:51 Stone, Joshua I [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-25 18:54 Stone, Joshua I
2006-10-26 1:07 ` Frank Ch. Eigler
2006-10-24 0:29 Stone, Joshua I
2006-10-24 15:16 ` David Smith
2006-10-20 18:44 Stone, Joshua I
2006-10-20 19:26 ` David Smith
2006-10-20 19:32 ` Frank Ch. Eigler
2006-10-20 19:50 ` David Smith
2006-10-20 20:13 ` Frank Ch. Eigler
2006-10-23 20:36 ` David Smith
2006-10-19 20:33 Stone, Joshua I
2006-10-19 20:41 ` David Smith
2006-10-06 19:08 Frank Ch. Eigler
2006-10-06 20:33 ` David Smith
2006-10-06 20:40 ` Frank Ch. Eigler
2006-10-19 19:49 ` David Smith
2006-10-19 21:53 ` Frank Ch. Eigler
2006-10-20 13:50 ` David Smith
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=C56DB814FAA30B418C75310AC4BB279DCC4312@scsmsx413.amr.corp.intel.com \
--to=joshua.i.stone@intel.com \
--cc=dsmith@redhat.com \
--cc=fche@elastic.org \
--cc=systemtap@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).