Community
Participate
Working Groups
This will gain us at least the following: 1. no need to setup and start stap-server 2. no need to configure and connect to server in the plugin / fewer user clicks 3. no need for escalated privileges for many things This simplifies to make it easier for users to try stuff. And if a tool requires too many preparational steps many will give up.
(In reply to comment #0) > This will gain us at least the following: > 1. no need to setup and start stap-server Maybe there is something wrong with the manual, but you don't need to set up stap-server to run SystemTap locally or remotely. The plugin uses ssh to run SystemTap in both cases. So to use it locally you need to set up a ssh server in the local machine and use it as it was a remote machine. > 2. no need to configure and connect to server in the plugin / fewer user > clicks That would be really nice. Local systemtap should be the default and it should run it without using ssh. If the user needs remote systemtap he/she could set that up in the preferences. > 3. no need for escalated privileges for many things > > This simplifies to make it easier for users to try stuff. And if a tool > requires too many preparational steps many will give up.
I've added functionality and api to run a stap script locally in commit 0a3006a The ability to access the 'run locally' option will be added in the fix for https://bugs.eclipse.org/bugs/show_bug.cgi?id=388533
Closing as I just verified it works.
