[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} ?

From: SCHAER Frederic <frederic.schaer@xxxxxx>
> Date: 01/15/2016 03:55 AM
> 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.

There's an issue with the way Fedora / Red Hat implemented the sysctl.d -
the init script looks for any file in there except for the ignored ones,
namely .bak, .orig, .rpmnew, .rpmorig, and .rpmsave; so a .txt file would
be passed to sysctl at boot, so it would have to be formatted as comments.
The new sysctl --system option only looks at .conf files, so that's an
unfortunate discrepancy.

> Another suggestion : since this kernel tuning only seems valid for the
> linux platform as the documentation suggests, would it be possible that
> the default script logs the kernel tuning it does in the syslogs  (via the
> logger command) in addition to any other logging mechanism ?
> I have the feeling that such system changes belong to be logged in the
> syslogs too, not just condor logs ?

That's a good idea - it'd be an easy add to the tuning script in the
increase and set functions, "logger -t htcondor".

        -Michael Pelletier.