Your message dated Fri, 03 Feb 2017 03:22:14 +0000
with message-id <[email protected]>
and subject line Re: [initscripts] does not mount /tmp as tmpfs
has caused the Debian Bug report #711963,
regarding [initscripts] does not mount /tmp as tmpfs
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
711963: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711963
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Package: initscripts
Version: 2.88dsf-41
Severity: normal
- --- Please enter the report below this line. ---
Just edited /etc/default/tmpfs to:
# 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=40%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
restarted and "df -h"
Filesystem Size Used Avail Use%
Mounted on
rootfs 51G 15G 35G 31% /
udev 10M 0 10M 0%
/dev
tmpfs 387M 404K 387M 1%
/run
/dev/disk/by-uuid/e3bed4b4-b9c5-4e74-bcf1-71a907da7cc7 51G 15G 35G 31% /
tmpfs 5.0M 0 5.0M 0%
/run/lock
tmpfs 2.0M 0 2.0M 0%
/run/shm
/dev/sda1 62M 21M 39M 35%
/boot
/dev/sda4 184G 61G 122G 34%
/home
There are no tmpfs defined in /etc/fstab:
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <fsck_order>
UUID=e3bed4b4-b9c5-4e74-bcf1-71a907da7cc7 / btrfs
defaults,noatime,discard,ssd 0 0
UUID=8a672a75-d090-4cb8-a050-c0fdcb3b0115 /boot auto defaults
0 2
#UUID=f9a10b80-babe-4fc6-b68f-d18707fcbb19 /var auto defaults
0 3
#UUID=ca7511b7-e034-44cb-9705-b08a653ceeb2 /tmp auto defaults
0 0
UUID=6153e457-b7ad-4a1b-b7b7-93c579e67cfd none swap sw
0 0
UUID=ba3d46f5-2616-42cf-b75d-314aa79df47c /home btrfs
defaults,noatime,discard,ssd 0 4
- --- System information. ---
Architecture: amd64
Kernel: Linux 3.2.0-4-amd64
Debian Release: jessie/sid
500 wheezy linux.dropbox.com
500 testing ftp.at.debian.org
500 stable dl.google.com
500 stable deb.opera.com
- --- Package information. ---
Depends (Version) | Installed
===================================-+-=================
libc6 (>= 2.4) |
mount (>= 2.11x-1) |
debianutils (>= 4) |
lsb-base (>= 3.2-14) |
sysvinit-utils (>= 2.86.ds1-64) |
sysv-rc |
OR file-rc |
coreutils (>= 5.93) |
Recommends (Version) | Installed
=========================-+-===========
psmisc | 22.20-1
e2fsprogs | 1.42.5-1.1
Package's Suggests field is empty.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
iEYEARECAAYFAlG3Q0oACgkQ6aU4/+gLeBn/LQCfd1xEfTSKgpq4jK/njq5Za1mq
JrYAn23flhe+3RWel1jo7idtQe7zpXT9
=Pn9p
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
On Thu, 17 Nov 2016 12:01:24 +0100 Maxime Chatelle <[email protected]> wrote:
>
> Just some information for other users that land here like me:
>
> It works fine with sysvinit but fail with systemd mainly because the
> script that do the job is part of sysvinit (look at the top of the bug
> page "Source for initscripts is src:sysvinit" ;) ).
Indeed. I don't know about the original report, but in the two follow-
ups reportbug showed the init system as systemd.
[...]
> So the best bet with systemd is to add a line in fstab by yourself.
[...]
Right. I never understood why initscripts has an extra config file for
this.
Ben.
--
Ben Hutchings
Anthony's Law of Force: Don't force it, get a larger hammer.
signature.asc
Description: This is a digitally signed message part
--- End Message ---
_______________________________________________
Pkg-sysvinit-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-sysvinit-devel
