From: Rodrigo Vivi <rodrigo.vivi@gmail.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH 3/4] tools: intel_gpu_abrt checking for root access
Date: Thu, 13 Dec 2012 14:11:23 -0200 [thread overview]
Message-ID: <1355415084-8431-3-git-send-email-rodrigo.vivi@gmail.com> (raw)
In-Reply-To: <1355415084-8431-1-git-send-email-rodrigo.vivi@gmail.com>
needed by other igt tools that are collecting more usefull information.
---
tools/intel_gpu_abrt | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/tools/intel_gpu_abrt b/tools/intel_gpu_abrt
index fe3684d..9ca58c0 100755
--- a/tools/intel_gpu_abrt
+++ b/tools/intel_gpu_abrt
@@ -1,5 +1,10 @@
#!/bin/sh
+if [[ $UID -ne 0 ]]; then
+ echo "$0 must be run as root"
+ exit 1
+fi
+
get(){
if [ ! -e $tardir/${@:$#} ] ; then
mkdir -p $tardir/${@:$#}
--
1.7.11.7
next prev parent reply other threads:[~2012-12-13 16:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 16:11 [PATCH 1/4] tools: intel_gpu_abrt "get" function Rodrigo Vivi
2012-12-13 16:11 ` [PATCH 2/4] tools: intel_gpu_abrt collecting more useful info Rodrigo Vivi
2012-12-13 16:11 ` Rodrigo Vivi [this message]
2012-12-13 16:11 ` [PATCH 4/4] tools: intel_gpu_abrt bug report template Rodrigo Vivi
2012-12-13 17:16 ` Daniel Vetter
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=1355415084-8431-3-git-send-email-rodrigo.vivi@gmail.com \
--to=rodrigo.vivi@gmail.com \
--cc=intel-gfx@lists.freedesktop.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