public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Vara Prasad <prasadav@us.ibm.com>
Cc: systemtap@sources.redhat.com
Subject: Re: marking tapset files
Date: Wed, 15 Nov 2006 20:27:00 -0000	[thread overview]
Message-ID: <20061115200522.GB4162@redhat.com> (raw)
In-Reply-To: <455B70A4.7030307@us.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 653 bytes --]

Hi -

varap wrote:

> [...]  Any resolution on this.

One minor tweak already done is the inclusion of a README file in
/usr/share/systemtap/tapset which says "don't run these!" (with more
words).

> I had to deal with two users in the last week who ran to this very
> problem of directly executing tapsets as scripts.  My proposal would
> be let us change the extension of tapsets as .tap and scripts to
> remain as .stp

Do you believe that this measure, by itself, would have been enough to
keep your users from running them directly?

> Next step we could enhance translator to give better error messages.

Let's open a bug report for that.

- FChE

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-11-15 20:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-27 13:20 Frank Ch. Eigler
2006-10-27 15:14 ` Mike Mason
2006-10-27 15:34   ` Frank Ch. Eigler
2006-10-27 16:30     ` Vara Prasad
2006-11-15 20:05       ` Vara Prasad
2006-11-15 20:27         ` Frank Ch. Eigler [this message]
2006-12-04 22:16           ` Vara Prasad
2006-12-05  0:07             ` Frank Ch. Eigler
2006-12-05  1:34               ` Vara Prasad
2006-10-27 15:33 ` Vara Prasad

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=20061115200522.GB4162@redhat.com \
    --to=fche@redhat.com \
    --cc=prasadav@us.ibm.com \
    --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).