What is the correct way to freeze the ulimit -n setting?

Question

linux

Hello.
the value of the open files parameter is not enough for me

core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 6190564
max locked memory       (kbytes, -l) 64
max memory size         (kbytes, -m) unlimited
open files                      (-n) 1024
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) 6190564
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited

I increased it
ulimit -n 16348
BUT when the OS is restarted, the parameter is reset to the previous 1024 again
. How to freeze this value correctly?

Answer 1

https://singztechmusings.wordpress.com/2011/07/11/...

Answer 2

Add to the /etc/security/limits.confappropriate entry.

Answer 3

Cities:
id, name
Streets
id, city_id, name
Subscribers
id, full name, city_id, street_id, house, apartment, phone, soap, age, gender, ceiling
Accounts
id, subscriber_id, balance
Query "Retrieve all subscribers with a balance of 3 rubles"
SELECT * accounts WHERE balance==3 LEFT JOIN subscribers ON subscriber.id=balancec.subscriber_id and join other tables if necessary
Pull all subscribers from city YYY
SELECT * FROM subscribers WHERE city_id==YYY

Answer 4

It seems to me that the table of the form (id; value; parent_id) is not suitable, there is not enough one more field "record type" (city / house / etc.). a multi-level hierarchy is obtained .... (for example, there is no private sector and no apartments).
I would build a 4 directory city, street, house number, apartment + type table (id, city id, street id, house number id, apartment id, subscriber's personal account) and all this into an index cluster ...
something like this

Answer 5

And where is your hierarchy then?) Maybe I didn’t understand something.
5 columns. normal relational table.
Subscriber's personal account
| id | value |
| 5999 | 8787878787|
city
​​| id | value |
| 5999 | Moscow |
| 5998 | Peter |
etc. when displaying, simply display everything from the tables with the desired ID.

Answer 6

Yes, here's the actual hierarchy:
city --
street
--- house number
----- apartment
------- subscriber's personal account.
In your answer, you probably meant that you need to create 5 tables:
City (id, value);
street(id; value; FK_city);
house number (id; value; fk_street);
apartment (id; value; fk_house_number);
personal account (id; value; fk_apartment).
Actually, we are struggling to either do this, or make one hierarchical table of the form - a file cabinet (id; value; parent_id).
So the question is, who has a lot of experience with hierarchical tables, what is more convenient in this case? what could be the problems?

Answer 7

Может лучше отталкиваться от КЛАДРа какого-нибудь?