From: Daniel.Thibault@drdc-rddc.gc.ca (Thibault, Daniel)
Subject: [lttng-dev] Having Trouble with LTTng folders
Date: Tue, 19 Nov 2013 16:48:35 +0000 [thread overview]
Message-ID: <48CF5AC71E61DB46B70D0F388054EFFD267A2B39@VAL-E-01.valcartier.drdc-rddc.gc.ca> (raw)
Date: Tue, 19 Nov 2013 08:43:17 -0500
From: Michael Steppe <msteppe91@gmail.com>
> I have set up another VM that only has a root account. Using Active Directory, I set up user accounts from my work's development network (giving everyone here at work the ability to sign in with their usernames and passwords), meaning root does not have permissions to edit files owned by these users. Here lies my problem:
>
> Let's say I sign in to the remote VM as user = "Scott". When I try and attempt to perform the "create" command through my plugin, I get:
>
> An error was encountered on 10.176.15.180 (10.176.15.180)
> Host: 10.176.15.180
> Command: /usr/bin/lttng create TRACE_111913_082211 -o /tmp/TRACE_111913_082211
> Exit Code: 1
> No output stream captured
> Error Output:
> Error: Unable to create config file
> Error: Command error
>
> I am assuming it is unable to create the config file because all the tracing folders and files are created and owned by root and root does not have access to write to Scott's home directory, where the config file should go. The trace is actually created, but not .lttngrc file is created.
> If I perform an 'lttng list" in the remote VM (signed in as Scott), I can see the TRACE_<date>_<time> and that its status is [inactive] (because we haven't started the trace yet).
>
> My question is this. Is there a way, in this version of LTT, to have the .lttng and .lttngrc folder/file to be located somewhere else? That way, all the tracing is done by root and the trace files are stored in /tmp and when the tracing is finished, root can give Scott ownership of the trace files?
I think you need to change your $HOME when issuing the lttng command. If 'Scott' has sudo privileges, you could prefix your lttng commands with 'sudo -H ' and that would do the trick. Otherwise, just prefix the lttng command with 'HOME=/root '. This must be done with all lttng commands, because the client looks .lttngrc up every time (unless you use the --session option common to nearly all commands).
Daniel U. Thibault
Protection des syst?mes et contremesures (PSC) | Systems Protection & Countermeasures (SPC)
Cyber s?curit? pour les missions essentielles (CME) | Mission Critical Cyber Security (MCCS)
R & D pour la d?fense Canada - Valcartier (RDDC Valcartier) | Defence R&D Canada - Valcartier (DRDC Valcartier)
2459 route de la Bravoure
Qu?bec QC G3J 1X5
CANADA
Vox : (418) 844-4000 x4245
Fax : (418) 844-4538
NAC : 918V QSDJ <http://www.travelgis.com/map.asp?addr=918V%20QSDJ>
Gouvernement du Canada | Government of Canada
<http://www.valcartier.drdc-rddc.gc.ca/>
next reply other threads:[~2013-11-19 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 16:48 Thibault, Daniel [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-11-19 13:43 Michael Steppe
2013-11-19 13:38 [lttng-dev] Having trouble " Michael Steppe
2014-02-03 15:56 ` Mathieu Desnoyers
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=48CF5AC71E61DB46B70D0F388054EFFD267A2B39@VAL-E-01.valcartier.drdc-rddc.gc.ca \
--to=daniel.thibault@drdc-rddc.gc.ca \
/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