perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

Hi,

It is still the case that it should only be running on new install. My guess is the recent package name in 3.5.1 confused it and it thought it was a new install so they got applied (i.e. the package with the old perfSONAR_PS-Toolkit-sysctl was removed and the renamed perfsonar-toolkit-sysctl package was added). You should be good going forward. Your other option is to run one of our non-toolkit bundles like perfsonar-core (see http://docs.perfsonar.net/install_options.html) but you also lose the Web UI as well.

Thanks,

Andy

On April 5, 2016 at 5:44:33 AM, Kevin Draai () wrote:

Hi 

Referring to the email thread sent in October 2014 below it seems that our sysctl.conf file is still going back to the default settings after the box is restarted after an update. The default settings are appended to the end of the file thus overriding our settings. For our tests over our longer links this affects the test results massively. 

So 2 questions:

1 - Is there perhaps a way in which we could turn off changes to the sysctl.conf file?

2 - What do you recommend we do?

Thanks

Kevin

SANReN Engineer - CSIR Meraka Institute

Email: |
Tel:  +27 12 841 2342
Fax:  +27 12 841 4223
http://www.sanren.ac.za

Hey Joseph,

On Oct 3, 2014, at 9:11 AM, Joseph Bernard <> wrote:

> Whenever we do updates, the sysctl.conf file goes back to default settings causing our results to go in the toilet.  Is there a way to protect this file from being overwritten?

With the 3.4 release, we’ll no longer be overwriting the sysctl.conf settings. They’ll only be set on new installs.

Cheers,

Aaron