> What happens if two packages want to set a sysctl to different values ?
that's why they are prefixed with numbers, the higher number will take effect
eg. 99-foobar.conf
sometimes we have conventions for number ranges like this
http://fedoraproject.org/wiki/Fontconfig_packaging_tips#Choosing_a_ruleset_numeral_prefix
50 User overrides
51 Local system overrides
...
that's why they are prefixed with numbers, the higher number will take effect
eg. 99-foobar.conf
sometimes we have conventions for number ranges like this
http://fedoraproject.org/wiki/Fontconfig_packaging_tips#Choosing_a_ruleset_numeral_prefix
50 User overrides
51 Local system overrides
...
On Fri, Mar 16, 2012 at 8:56 PM, Chris Adams <cmadams@xxxxxxxxxx> wrote:
Once upon a time, Chris Adams <cmadams@xxxxxxxxxx> said:My appologies; I misread "sysrq" as "sysctl".
> Once upon a time, Matthew Garrett <mjg59@xxxxxxxxxxxxx> said:
> > On Fri, Mar 16, 2012 at 10:57:13AM -0500, Chris Adams wrote:
> > > Once upon a time, Matthew Garrett <mjg59@xxxxxxxxxxxxx> said:
> > > > No package should be automatically changing the sysrq policy.
> > >
> > > Why not?
> > >
> > > For example, I use a commercial backup program that makes extensive use
> > > of IPC and needs the msgmni and msgmnb limits raised beyond the default
> > > values. Why shouldn't they be able to include that change in their RPM?
> >
> > Where did I say they shouldn't?
>
> You mean other than the quoted line?
--
Chris Adams <cmadams@xxxxxxxxxx>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel