1 |
On Tue, Jul 28, 2020 at 3:13 PM Mike Gilbert <floppym@g.o> wrote: |
2 |
> |
3 |
> On Tue, Jul 28, 2020 at 2:50 PM Zoltan Puskas <zoltan@×××××××××.info> wrote: |
4 |
> > |
5 |
> > Hi, |
6 |
> > |
7 |
> > I've upgraded to and running systemd-246_rc2 on one of my systems and |
8 |
> > noticed that tmpfs mounted directories are significantly smaller. |
9 |
> > |
10 |
> > This is because with commit |
11 |
> > https://github.com/systemd/systemd/commit/7d85383edbab73274dc81cc888d884bb01070bc2 |
12 |
> > they have changed them to be 10% of the physical memory instead of the |
13 |
> > default of 50%. |
14 |
> > |
15 |
> > This is a potentially breaking, or at least an unexpected behaviour |
16 |
> > change, especially for people using tmpfs on /tmp for compiling. |
17 |
> > |
18 |
> > Maybe we should make a news item to let people know that they either |
19 |
> > need to add an fstab entry with size option set, or better, create a |
20 |
> > systemd local override with relevant content. |
21 |
> |
22 |
> Don't use /tmp for PORTAGE_TMPDIR. /tmp is meant for small temporary |
23 |
> storage. If you want to compile in a tmpfs, set up a separate mount |
24 |
> point for it. |
25 |
> |
26 |
> I don't intend to create a news item for this, but I would not object |
27 |
> to someone else doing it. |
28 |
|
29 |
Also, the limit for /tmp is likely to change again before the 246 final release. |
30 |
|
31 |
https://github.com/systemd/systemd/pull/16576 |