Phil, it does work if /mnt is already a mount point, and I subsequently
make a second mount underneath /mnt.
I expect that the patched version of unshare(1) with restore the
previous behavior, allowing things mounted directly on /mnt to be private.
Thanks,
Jim
On 06/06/2015 10:34 AM, James Long wrote:
Responding for others who find this on the web:
On 06/05/2015 10:03 AM, Phil Susi wrote:
On 6/5/2015 11:00 AM, James Long wrote:
So the mount is still visible to other processes, and doesn't exit with
the process, as it used to in wheezy. The same thing happens with
--make-private. What am I doing wrong?
I believe you need to --make-private first, *then* mount the fs. The
inheritance setting applies to whether new mounts are also mounted in
other namespaces, not whether other namespaces currently can see the
mount.
I appreciate the suggestion, but it still doesn't work:
1st login window:
$ sudo unshare -m /bin/bash
# mount --make-private /mnt
mount: /mnt is not mountpoint or bad option
In some cases useful info is found in syslog - try
dmesg | tail or so.
# mount -t nfs -o ro,vers=3,tcp 10.4.5.101:/opt /mnt
# df -Th | grep mnt
10.4.5.101:/opt nfs 92G 17G 71G 20% /mnt
2nd login window, the mount is still visible:
$ df -Th | grep mnt
10.4.5.101:/opt nfs 92G 17G 71G 20% /mnt
Applying "mount --make-private /mnt" again in the 1st window still
leaves the mount visible in the 2nd window.
Thanks,
Jim
--
James Long
Information Systems Manager
International Arctic Research Center
University of Alaska Fairbanks
jlong15 at alaska.edu
(907) 474-2440
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
