There are no logs of the remote commands execution on the machine that execute them 3) Business Requirements Satisfied By Request: being able to get these logs from the machine, not only spacewalk 4) Functional Requirements That Are Not Presently Possible: those logs are only present in spacewalk 5) What Will Success Look Like: a new log file holding the results will be created on the machine with details that would otherwise be available from spacewalk
Implementing this would mean that the output of scripts run as root would end up on the client-machine's drive. There are some security and disk-space issues that come to mind. To give the admin of the client-machine (as possibly separate from the spacewalk-admin that can arrange for remote-cmds to run on the client) more control of the impacts to their machine, propose adding two new settings to /etc/sysconfig/rhn/rhncfg-client.conf : script_log_file = /var/log/rhn/rhncfg-actions.log script_log_file_enable = 1 If script_log_file_enable = 0, we don't log on the client. script_log_file should have 600 perms for root, only.
spacewalk commit 9f89d22a515a710ceaadd475a000d3827061c2ae
Fix for this bug is present in Spacewalk 2.0, closing this bug as CURRENTRELEASE.