Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: anand.neeli@gmail.com (Anand Neeli)
Subject: [lttng-dev] Warning: HOME environment variable not set.
Date: Sat, 11 Apr 2015 04:42:17 +0530	[thread overview]
Message-ID: <CAM5kDqwuyWS4KvAHXXmFf0aBvRD=3c3uZdrUVH0H+dP8H1H1rA@mail.gmail.com> (raw)
In-Reply-To: <218306271.74676.1427117803698.JavaMail.zimbra@efficios.com>

What will be the effect of HOME env var not being set?
cant the app log without this env var? or can we ignore this warning?

Thanks,
Anand Neeli


On Mon, Mar 23, 2015 at 7:06 PM, Mathieu Desnoyers <
mathieu.desnoyers at efficios.com> wrote:

> Perhaps your program is clearing its environment
> variables ? Or launched by a wrapper that clears
> the env. var. ?
>
> Can you try with a simple demo program to find our
> what is clearing those ?
>
> Thanks,
>
> Mathieu
>
>
> ------------------------------
>
> Hi All,
> I'm sorry to bump on this thread again.
>
> Is there any way to overcome this issue?
>
> Thanks,
> Anand Neeli
>
> On Wed, Mar 18, 2015 at 10:01 PM, Chidhu R <chid1989 at gmail.com> wrote:
>
>> I too am getting the same errors. Inspite of setting LTTNG_HOME in my
>> program.
>>
>> On Tue, Mar 17, 2015 at 2:18 PM, Anand Neeli <anand.neeli at gmail.com>
>> wrote:
>>
>>> Hi All,
>>>
>>> any idea when do we get this error?
>>>
>>> app: libust[4745/4745]: Warning: HOME environment variable not set.
>>> Disabling LTTng-UST per-user tracing. (in setup_local_apps() at
>>> lttng-ust-comm.c:385)
>>> app: libust[4751/4751]: Warning: HOME environment variable not set.
>>> Disabling LTTng-UST per-user tracing. (in setup_local_apps() at
>>> lttng-ust-comm.c:385)
>>> app: libust[4760/4760]: Warning: HOME environment variable not set.
>>> Disabling LTTng-UST per-user tracing. (in setup_local_apps() at
>>> lttng-ust-comm.c:385)
>>> app: libust[4780/4780]: Warning: HOME environment variable not set.
>>> Disabling LTTng-UST per-user tracing. (in setup_local_apps() at
>>> lttng-ust-comm.c:385)
>>>
>>> i have set LTTNG_HOME=HOME=/home/root
>>> using 2.6
>>>
>>> Thanks,
>>> Anand Neeli
>>>
>>>
>>> _______________________________________________
>>> lttng-dev mailing list
>>> lttng-dev at lists.lttng.org
>>> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
>>>
>>>
>>
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
>
>
>
>
> --
> Mathieu Desnoyers
> EfficiOS Inc.
> http://www.efficios.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20150411/0a430a6b/attachment.html>


       reply	other threads:[~2015-04-10 23:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAM5kDqw2R5+xy9t+sjet_PWt2+2fPh5ijbkKB_15NUJQUoKU5Q@mail.gmail.com>
     [not found] ` <CAL1ZhOM+RTpz2iiqYEM2RHTCK+PxBAXk54q8ykmnsac0-w4WoA@mail.gmail.com>
     [not found]   ` <CAM5kDqxMTOj0TqZQjT0i+0MHmPxfvPUocgV0_erw4_7+pBtSDA@mail.gmail.com>
     [not found]     ` <218306271.74676.1427117803698.JavaMail.zimbra@efficios.com>
2015-04-10 23:12       ` Anand Neeli [this message]
2015-04-10 23:57       ` Philippe Proulx
2015-04-11  0:31         ` Anand Neeli

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='CAM5kDqwuyWS4KvAHXXmFf0aBvRD=3c3uZdrUVH0H+dP8H1H1rA@mail.gmail.com' \
    --to=anand.neeli@gmail.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