On Mon, Jun 13, 2011 at 09:59:53AM +0200, Matteo Sessa wrote:
>
> Is there a chance of having this committed for the upcoming release?
>
> I've internally backported the patch to the stable rhncfg-5.9.52.
> I'm actively using that in production and it's doing quite well.
I have committed your pa
uot;
To: spacewalk-devel@redhat.com
Sent: Tuesday, May 31, 2011 12:28:58 PM
Subject: Re: [Spacewalk-devel] Remote commands temporary file location
A quick fix to the patch. I've missed an mkdir in the spec. Now it builds
correctly.
- Original Message -
From: "Matteo Sessa&qu
Dne 31.5.2011 12:28, Matteo Sessa napsal(a):
Attached is a patch to implement solution #2 from my previous request.
I will check it.
@Mirek
I've made some changed to the rhncfg spec file too to create the new default
directory, do I need to update the changelog and/or the release number or
A quick fix to the patch. I've missed an mkdir in the spec. Now it builds
correctly.
- Original Message -
From: "Matteo Sessa"
To: spacewalk-devel@redhat.com
Sent: Tuesday, May 31, 2011 11:40:53 AM
Subject: Re: [Spacewalk-devel] Remote commands temporary file location
H
Hi,
Attached is a patch to implement solution #2 from my previous request.
/usr/share/rhn/actions/script.py now imports some libs for configuration file
access and reads "script_tmp_dir" parameter from rhncfg-client.conf, if unset
it will fallback to the previous behavior and use /tmp as usual.
- Original Message -
From: "Luc de Louw"
To: spacewalk-devel@redhat.com
Sent: Tuesday, May 31, 2011 9:31:03 AM
Subject: Re: [Spacewalk-devel] Remote commands temporary file location
> Hi,
>
> Unfortunately the noexec mount option does not help that much to prevent
On 05/30/2011 02:27 PM, Matteo Sessa wrote:
Hi all,
I'm regularly using spacewalk to issue remote commands on my systems after
configuration files deploy and I've noticed that the
/usr/share/rhn/actions/script.py library that perform the script execution
temporarily write the provided script
Dne 30.5.2011 14:27, Matteo Sessa napsal(a):
I'm regularly using spacewalk to issue remote commands on my systems after
configuration files deploy and I've noticed that the
/usr/share/rhn/actions/script.py library that perform the script execution
temporarily write the provided script inside /
Hi all,
I'm regularly using spacewalk to issue remote commands on my systems after
configuration files deploy and I've noticed that the
/usr/share/rhn/actions/script.py library that perform the script execution
temporarily write the provided script inside /tmp/rhn-remote-script by default.
Acco
