Bug#688412: configuration error?

[Matus UHLAR - fantomas]

>> >On Tue, 16 Jul 2019, Matus UHLAR - fantomas wrote:
>> >> IIRC people using systemd were advised to use fstab to manipulate /tmp
>> >> mount options.

>> On 16.07.19 17:18, Thorsten Glaser wrote:
>> >Yes, but systemd does not use /etc/default/tmpfs, so…

>[2019-07-16 17:23] Matus UHLAR - fantomas <uhlar at fantomas.sk>
>> ...which is exactly why I found it strange to have /tmp in fstab and yet
>> expect using /etc/default/tmpfs.
>>
>> in case of /tmp in fstab, options should be in fstab too.

On 18.07.19 12:45, Dmitry Bogatov wrote:
>Maybe I am missing some context, but /etc/default/tmpfs provides feature
>(not always working, as proved by current bug) to set size by percentage
>of available RAM. This is not supported by mount(8).

No, it's not supported by mount, it's used in /lib/init/tmpfs.sh which is
called from mountkernfs.sh, which is not called when systemd is used as init
system.

>Whether such feature warranted its complexity is good question, but now
>people rely on it. I think so.

I don't think this ever worked and it surely would add (at least)
unnecessary complexity there.

Note that tmpfs(5) manual page notes that the defaults may be overridden by
fstab (multiple times).

simply said, if anyone configures /tmp in /etc/fstab, they should configure
all its parameters there too and not rely on /etc/default/tmpfs.

I believe this bug should be closed...
-- 
Matus UHLAR - fantomas, uhlar at fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
I'm not interested in your website anymore.
If you need cookies, bake them yourself.