On 06/21/2011 10:09 AM, Siva Velusamy wrote:
>
>
> On Tue, Jun 21, 2011 at 9:47 AM, Corey Ashford
> mailto:cjash...@linux.vnet.ibm.com>> wrote:
>
> On 06/21/2011 05:54 AM, Daniel HB wrote:
>
> Hey Corey!
>
> I think it's a good idea but I don't think, unfortunately, that is
On Tue, Jun 21, 2011 at 9:47 AM, Corey Ashford
wrote:
> On 06/21/2011 05:54 AM, Daniel HB wrote:
>
>> Hey Corey!
>>
>> I think it's a good idea but I don't think, unfortunately, that is
>> simple to implement in the case of the Oprofile plugin. It uses a script
>> to add an entry in the sudoers (S
On 06/21/2011 05:54 AM, Daniel HB wrote:
Hey Corey!
I think it's a good idea but I don't think, unfortunately, that is
simple to implement in the case of the Oprofile plugin. It uses a script
to add an entry in the sudoers (Suse) or add a security wrapper for
consolehelper (RHEL). After that it
Hey Corey!
I think it's a good idea but I don't think, unfortunately, that is
simple to implement in the case of the Oprofile plugin. It uses a script
to add an entry in the sudoers (Suse) or add a security wrapper for
consolehelper (RHEL). After that it executes the tool using a symbolic
link loc
Hi Folks,
We have an interesting challenge with the Linux Tools Project plug-ins,
and that is being able to determine where each of the linux tool
executables are. I think for most users of the plug-ins, they can
assume that all of the tools are on their search path, for example
/usr/bin/opcontro
