[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [HTCondor-users] why does htcondor change sysctl params, and why is this done outside of /etc/sysctl.{d, conf} ?

On 1/15/2016 3:54 AM, SCHAER Frederic wrote:
> So, to be back on this : may I suggest that if sysctl.d directory
> exists, a .txt file is put in there by the condor default tuning
> script if that's the one that's used ? I'm assuming that if/when
> people change the default tuning script, they will know what they are
> doing, and nothing has to be done then by condor.

Irony. Having two (or more) different possible locations for the kernel
tuning script is the opposite of standardization and consistency. Like
it or not, what Condor does today is consistent across every Linux
distribution. That's a big win for anyone who manages heterogeneous

> if you can touch the heart of the sytem, you can probably touch the
> brain, what's the difference ? If directory does not exist... the

The difference is who owns what. HTCondor is not part of the operating
system. Intruding on the operating system's domain should be avoided.

> tuning script can probably create it too and put a .txt inside, as
> this will cause no harm and the script must have root privileges to
> tune the kernel anyway.

Scripts do not belong in sysctl.d. The only files that belong there are
conf files and documentation provided by the vendor.

Regarding the logging of sysctl events, it's not a bad idea in principle
but off the top of my head I'm not sure what the best way to handle that
might be.

Rich Pieri <ratinox@xxxxxxx>
MIT Laboratory for Nuclear Science