Updates messing up limits.conf

Cory K. coryisatm at ubuntu.com
Sun Jun 8 16:37:10 BST 2008

hollunder at gmx.at wrote:
> "Cory K." <coryisatm at ubuntu.com> wrote:
>> hollunder at gmx.at wrote:
>>> Hi there, I just noticed that apparently, my limits.conf got reset.
>>> The @memlock is still there, but none of the other modifications.
>>> Thought I let you know.
>> In this situation I'm betting you accepted the maintainers version of
>> the file on the update rather than keeping your own. It's normally a
>> question that's asked. I've done it lately as well.
>> Any file that a user modifies like this usually should be asked this
>> question. Correct guys?
> Thanks for the answer.
> I think I remember doing that for something, thought it might be a good
> idea. This would mean tough that the maintainers version isn't Ubuntu
> Studios version with the @audio - rtprio 99 in it, right?

The "mantainers version" is vanilla Ubuntu. Studio edits the file in one
of our own packages. Also, users edit this file with the Ubuntu Studio
Controls app. So, users must be aware on upgrade that they need to keep
their version and or look at the diff in the proposed new version.

Same thing happens usually with samba and apache for me.

-Cory K.

More information about the Ubuntu-Studio-devel mailing list