On 3/4/2012 11:22 PM, David Goulet wrote: > Actually it does. If you type: lttng create test -o /tmp/test > > /tmp/test is created and empty. > Yeah, that was meant as a reply for Ryan. > > > Anyway, i just noticed a problem with relative paths: > > (~)> lttng > > LTTng Trace Control 2.0.0-rc2 > > (~)> lttng create --output traces session > > Error: Create directory failed > > (~)> lttng create --output ./traces session > > Error: Create directory failed > > (~)> lttng create --output /root/traces session > > Session session created. > > Traces will be written in /root/traces > > I've just tested it. The trace output directory, given without a full > path, is > created at the $PWD of the session daemon. If the directory exist, it will > simply write the trace in it. > > So, the error you have are probably related to a location you don't > have write > access..... > > I agree that the relative path could be handle better and use the current > directory of the user using "lttng". I was missing the fact that the *daemon* creates the directory. Thanks for clarify it. Definitely use the current directory of lttng for relative paths would be better. > > Thanks! > David > > Thanks, Ettore
_______________________________________________ lttng-dev mailing list [email protected] http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
