Your message dated Fri, 13 Apr 2018 09:58:52 +0200
with message-id <20180413075852.GL21524@vis>
and subject line [ Accepted libpam-mount 2.16-5 (source) 
into unstable]
has caused the Debian Bug report #627085,
regarding does not detect tmpfs already mounted unless "path" attribute provided
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

Debian Bug Tracking System
Contact with problems
--- Begin Message ---
Package: libpam-mount
Version: 2.14-1
Severity: important

Using "tmpfs" to avoid an SSD being written to continuously, and to
discard files at reboot. I started off with a line like:

  <volume group="users" fstype="tmpfs" mountpoint="/home/%(USER)/mycache/" 
options="size=1G,uid=%(USER),mode=0700" />

If I logged in multiple times, however, i would get multiple tmpfs
mounted on top of each other, which is certainly wrong and not what I want
(eg, a loging would make all previous files in cache disappear!!).

By enabling verbose logging, turns out that:

1) pam-mount, at login, decides if a file systems needs to be mounted
again based on the output of mount, and content of /proc/mounts.
2) if a mount is already visible in /proc/mounts, it does not mount it.
If it is missing, it adds it.
3) with verbose logging, it seems like that without the "path" attribute
in the <volume> definition, path is interpreted as "(null)" and it looks
for '/' in the output of /proc/mounts? However, the linux kernel has
"none" in the same line (probably as a result of how it was mounted).
The two don't match, so the file system is mounted again and again.
4) if I add a "path" attribute to the <volume> definition, like with:

<volume group="users" fstype="tmpfs" path="mycache" 
mountpoint="/home/%(USER)/mycache/" options="size=1G,uid=%(USER),mode=0700" />

And then login and run mount, I now see:

mycache on /home/ccontavalli/mycache type tmpfs 

instead of:

none on /home/ccontavalli/mycache type tmpfs 

... and logging out now works.

What I'd like to see is either:
1) determine this is "expected behavior", and document it.
2) fix the code so an unspecified "path" is treated correctly (eg, doesn't
try to match for / or whatever it is trying to match on), and just does
the right thing.

2) is more desirable to me than 1).

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (995, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
Architecture: i386 (i686)

Kernel: Linux 3.10-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages libpam-mount depends on:
ii  base-files      7.2
ii  libc6           2.17-92+b1
ii  libcryptsetup4  2:1.6.1-1
ii  libhx28         3.15-2
ii  libmount1       2.20.1-5.5
ii  libpam-runtime  1.1.3-9
ii  libpam0g        1.1.3-9
ii  libpcre3        1:8.31-2
ii  libssl1.0.0     1.0.1e-3
ii  libxml2         2.9.1+dfsg1-3
ii  mount           2.20.1-5.5

libpam-mount recommends no packages.

Versions of packages libpam-mount suggests:
pn  cifs-utils  <none>
pn  davfs2      <none>
ii  fuse        2.9.2-4
ii  lsof        4.86+dfsg-1
pn  ncpfs       <none>
ii  openssl     1.0.1e-3
ii  psmisc      22.20-1
pn  sshfs       <none>
pn  tc-utils    <none>
pn  xfsprogs    <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
----- Forwarded message from Jochen Sprickerhof <> -----

Date: Thu, 12 Apr 2018 17:51:57 +0000
From: Jochen Sprickerhof <>
Subject: Accepted libpam-mount 2.16-5 (source) into unstable

Format: 1.8
Date: Thu, 12 Apr 2018 19:29:03 +0200
Source: libpam-mount
Binary: libpam-mount
Architecture: source
Version: 2.16-5
Distribution: unstable
Urgency: medium
Maintainer: Jochen Sprickerhof <>
Changed-By: Jochen Sprickerhof <>
libpam-mount - PAM module that can mount volumes for a user session
libpam-mount (2.16-5) unstable; urgency=medium
  * Upload to unstable.
f3346de2a4db56a7b992ee4e64653c3a3f7c4b6a 2035 libpam-mount_2.16-5.dsc
de0f92c4584e1ba8f3e9d4e30ae731fe41f2239c 28164 libpam-mount_2.16-5.debian.tar.xz
353ae563171aea5c0937b735dfca777700e31f22 5830 
f94b862dd63cd0f0cb7b3c656584df73aa3cb7d31aa8a178586bcbb7df2df741 2035 
42ea83dbca076bedcf9e37b3b24d0dad73aaf69cd3186301a69de5b8d33db1b0 28164 
9023fc1ce120d8a2925e44e360df3c7a8d64f4254d8b2f4803eb4eaa877777bb 5830 
656efc8641dbd2e25c5d5c1b0299f4d1 2035 admin optional libpam-mount_2.16-5.dsc
e2e4137472a4e41e1939677471d08759 28164 admin optional 
763fd31d812fc92b4b07dd0a4799b78b 5830 admin optional 

----- End forwarded message -----

Attachment: signature.asc
Description: PGP signature

--- End Message ---

Reply via email to