From owner-freebsd-bugs@freebsd.org Sat May 16 08:07:55 2020 Return-Path: Delivered-To: freebsd-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 11B2A2E9742 for ; Sat, 16 May 2020 08:07:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 49PHvZ6k7vz45Sm for ; Sat, 16 May 2020 08:07:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id E6A902E9741; Sat, 16 May 2020 08:07:54 +0000 (UTC) Delivered-To: bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E66E92E9740 for ; Sat, 16 May 2020 08:07:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49PHvZ5qKbz45Sl for ; Sat, 16 May 2020 08:07:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id C2CC3AA82 for ; Sat, 16 May 2020 08:07:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 04G87s9e076675 for ; Sat, 16 May 2020 08:07:54 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 04G87sAX076674 for bugs@FreeBSD.org; Sat, 16 May 2020 08:07:54 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 246496] automount: erroneously creates mount point hierarchy in current directory Date: Sat, 16 May 2020 08:07:54 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 12.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: d8zNeCFG@aon.at X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 May 2020 08:07:55 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D246496 Bug ID: 246496 Summary: automount: erroneously creates mount point hierarchy in current directory Product: Base System Version: 12.1-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: d8zNeCFG@aon.at Scenario: - running FreeBSD 12.1-RELEASE-p5 #5 r361008M - rc.conf contains autofs_enable=3D"YES" - automountd and autounmountd are running - /etc/auto_master is changed to contain additional hierarchies to be added - these hierarchies reference the same /etc/auto_* files as those enabled so far, albeit to be mounted at different locations - Specifically: /auto/backup auto_backup /auto/multimedia auto_multimedia /auto/netspace auto_netspace /auto/srcs auto_srcs /auto/system auto_system /auto/users auto_users /auto/vdisks auto_vdisks /auto/z auto_z #C /d/rpi-b/auto/backup auto_backup #C /d/rpi-b/auto/multimedia auto_multimedia #C /d/rpi-b/auto/netspace auto_netspace #C /d/rpi-b/auto/srcs auto_srcs #C /d/rpi-b/auto/system auto_system #C /d/rpi-b/auto/users auto_users #C /d/rpi-b/auto/vdisks auto_vdisks #C /d/rpi-b/auto/z auto_z - First, the leading '#C ' is removed, and then automount is called to re-s= can the modified auto_master Result: - In the directory where automount is being run, the mount hierarchy is cre= ated - Example (run in root's home dir): [0]# du ~root [...] 4 /root/d/rpi-b/auto/backup 4 /root/d/rpi-b/auto/multimedia 4 /root/d/rpi-b/auto/netspace 4 /root/d/rpi-b/auto/srcs 4 /root/d/rpi-b/auto/system 4 /root/d/rpi-b/auto/users 4 /root/d/rpi-b/auto/vdisks 4 /root/d/rpi-b/auto/z 36 /root/d/rpi-b/auto 40 /root/d/rpi-b 124 /root/d [...] [0]#=20 Expected result: - If at all, this hierarchy should be created in /d/rpi-b, not in /root/d/rpi-b. Note: the hierarchy in /d/rpi-b is created (later?) anyway (= when directories are actually mounted?). -- Martin --=20 You are receiving this mail because: You are the assignee for the bug.=