Bug#807769: systemd: /tmp mounted as tmpfs without user asking for it
Sanjoy Mahajan
sanjoy at mit.edu
Mon Dec 14 05:56:24 GMT 2015
You're right, the /etc/default/tmpfs does set RAMTMP. However,
/etc/fstab doesn't have an entry for /tmp (I don't have any partitions
other than /, except for /boot/efi). That may explain why my /tmp
wasn't on tmpfs until some action much after the boot forced that to
happen even though /tmp already existed as a subdirectory of / (on the /
partition).
> Please also attach /etc/default/tmpfs
# Configuration for tmpfs filesystems mounted in early boot, before
# filesystems from /etc/fstab are mounted. For information about
# these variables see the tmpfs(5) manual page.
# /run is always mounted as a tmpfs on systems which support tmpfs
# mounts.
# mount /run/lock as a tmpfs (separately from /run). Defaults to yes;
# set to no to disable (/run/lock will then be part of the /run tmpfs,
# if available).
#RAMLOCK=yes
# mount /run/shm as a tmpfs (separately from /run). Defaults to yes;
# set to no to disable (/run/shm will then be part of the /run tmpfs,
# if available).
#RAMSHM=yes
# mount /tmp as a tmpfs. Defaults to no; set to yes to enable (/tmp
# will be part of the root filesystem if disabled). /tmp may also be
# configured to be a separate mount in /etc/fstab.
RAMTMP=yes
# Size limits. Please see tmpfs(5) for details on how to configure
# tmpfs size limits.
#TMPFS_SIZE=20%VM
#RUN_SIZE=10%
#LOCK_SIZE=5242880 # 5MiB
#SHM_SIZE=
#TMP_SIZE=
# Mount tmpfs on /tmp if there is less than the limit size (in kiB) on
# the root filesystem (overriding RAMTMP).
#TMP_OVERFLOW_LIMIT=1024
More information about the Pkg-systemd-maintainers
mailing list