Dotaz: Systemd a hugetlbfs

[alkoholik]

Nejak mi unikla filozofie systemd pri praci s hugetlbfs.
Kdyz mam 2 ruzne velikosti hugepages (2M a 1G), tak mi systemd podle vseho do /dev/hugepages namounti ty 1G.
Udelal jsem si podle service dev-hugepages.mount druhou dev-hugepages2M.mount, kde jsem zmenil mountpoint na /dev/hugepages2M a prihodil Options=pagesize=2M.
Je tohle "spravny" pristup?
Trosku to saje, protoze na serveru bez 1G stranek mam v /dev/hugepages namountovane ty dvoumegove. Za idealni bych povazoval /dev/hugepages2M a /dev/hugepages1G, ale to bych si musel upravit balikovy dev-hugepages.mount, ne?

---

---

Odpovědi

[1john2]

Tak na debianu se jeste musi dev-hugepages2M.mount rucne nasymlinkovat do /lib/systemd/system/sysinit.target.wants/, aby se namountoval pri bootu.
Fakt zlaty /etc/fstab proti tomuhle.

[cezz]

Pokud chcete, aby se jednotka spouštěla při startu, potřebujete ji povolit:

systemctl enable dev-hugepages2M.mount

[alkoholik]

Tak presne o tomhle mluvim..

The unit files have no [Install] section. They are not meant to be enabled
using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
   .wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
   a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
   D-Bus, udev, scripted systemctl call, ...).