This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug translator/17410] New: let --remote optionally handle compilation from afar too
- From: "jistone at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Thu, 18 Sep 2014 17:55:47 +0000
- Subject: [Bug translator/17410] New: let --remote optionally handle compilation from afar too
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=17410
Bug ID: 17410
Summary: let --remote optionally handle compilation from afar
too
Product: systemtap
Version: unspecified
Status: NEW
Severity: enhancement
Priority: P2
Component: translator
Assignee: systemtap at sourceware dot org
Reporter: jistone at redhat dot com
Right now when using remote, you must either have a local environment for
compiling to the target, or enable a compile server for that. But there may be
cases where the remote targets are already capable of compiling stap modules
themselves, and we could let them do so directly.
The user would still get to write their script locally however they like, and
can also get the fanout of running it on multiple --remote targets at once.
This would have similar questions as the compile server as to what to ship from
the user to remote -- at least the script and -I tapsets, and all the options
except remote itself. But this wouldn't have the same security considerations
as the compile server, because --remote works as an authenticated user already.
A new --remote-compile option might be the trigger for this new behavior.
--
You are receiving this mail because:
You are the assignee for the bug.