From owner-freebsd-stable@freebsd.org Sat Jan 4 00:02:24 2020 Return-Path: Delivered-To: freebsd-stable@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 A08711D1BBE for ; Sat, 4 Jan 2020 00:02:24 +0000 (UTC) (envelope-from thenomad@gmail.com) Received: from mail-pf1-x42c.google.com (mail-pf1-x42c.google.com [IPv6:2607:f8b0:4864:20::42c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47qMQl49ZPz4WpL for ; Sat, 4 Jan 2020 00:02:23 +0000 (UTC) (envelope-from thenomad@gmail.com) Received: by mail-pf1-x42c.google.com with SMTP id x6so23082540pfo.10 for ; Fri, 03 Jan 2020 16:02:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:to:from:subject:message-id:date:user-agent:mime-version :content-language:content-transfer-encoding; bh=TR9JH1GH77NO1lkfwDMSVr5FjLKuWJJiRXOOHnRyK/U=; b=FKeBlLGVJmjXNVYDbVarxiS2PSm0x6Z3xHuSAMiB5eR7tx6PJfP+Mng/w6i3/aoZv8 yu1EnHxn5Ec+SVqnNbn4hKNtGNN8Pl1LpaXSExUx/Km2T2hwLYgqlYIjuQPZPTLzUn7h 28VY107fdlbErA75i7Pttrep9kGrdwCOm+W1JLSHDquTw/ghFuHSpeKJ3q5zUHolOIqo dL1ue8ddTfIgebIRwFZQcunP69h9wTpttiKvSMmd98P9wMbg8MNZLy+X6bwitj1+5IHp HCZPY/wFrC/Y8i5+uKyUwtpe2/UmRtLVvFQrO2zzchbqMahn0sk84/RpXr8u94ZCwgfp szSQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:to:from:subject:message-id:date :user-agent:mime-version:content-language:content-transfer-encoding; bh=TR9JH1GH77NO1lkfwDMSVr5FjLKuWJJiRXOOHnRyK/U=; b=j+/pF9BL6/Fa3LLxBlJj7edWI0J78wa5zyKD7JIpCsQgsClHGuxPEQOldSCXabLj1m zrXkP+QaSQTPpbZfEJRZAjzi4itJCYPmpV5Bnx6J62UHA4SBFZGPaHkTMEP3DRgle3TH 6kfIOpV/Y1jwGR3smIfymDCI6OFfFXx5bKayZPGKFM6EC1px4MqEg5RpSIz/TSmrcUXC Jih/Reydgc7kPegRjRLd/XYVuNFtpXeJNg7gtS9t4f+feKHbrTq4UpgPOcH5NJUjFDBN Lt0chdbZhaCZ/6HvyOsK2IWTErDZ9zOkU0LdpgIo+zzU0Z95+KlYkMr+DvoB3q6snWO4 PdOg== X-Gm-Message-State: APjAAAVD5fNSlAeHTd4WSPYPFIvwJlyhwlDFGuX3qB2oAq1J5NY2fR1Q XOFZSbbI4tfg7gB+gtIyqKJbtBn/ X-Google-Smtp-Source: APXvYqxICsDQpIJ0WyLFTB23TWNICZ9ngT1XPo055NsOiyxB9syX5s8bAHODeAnOH8pQvJe9ZXGAlQ== X-Received: by 2002:a05:6a00:8a:: with SMTP id c10mr85602399pfj.191.1578096141539; Fri, 03 Jan 2020 16:02:21 -0800 (PST) Received: from vanyel.ee.washington.edu (vanyel.ee.washington.edu. [128.208.232.99]) by smtp.gmail.com with ESMTPSA id e16sm62393863pgk.77.2020.01.03.16.02.20 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 03 Jan 2020 16:02:20 -0800 (PST) Sender: Lee Damon To: freebsd-stable@freebsd.org From: Lee Damon Subject: two questions about autofs on FBSD Message-ID: <578798e4-5e26-6116-9ffe-6dcc4f08ed59@castle.org> Date: Fri, 3 Jan 2020 16:02:19 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.3.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 47qMQl49ZPz4WpL X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=FKeBlLGV; dmarc=none; spf=pass (mx1.freebsd.org: domain of thenomad@gmail.com designates 2607:f8b0:4864:20::42c as permitted sender) smtp.mailfrom=thenomad@gmail.com X-Spamd-Result: default: False [-4.80 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[3]; DMARC_NA(0.00)[castle.org]; DKIM_TRACE(0.00)[gmail.com:+]; RCVD_IN_DNSWL_NONE(0.00)[c.2.4.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; IP_SCORE(-2.60)[ip: (-8.92), ipnet: 2607:f8b0::/32(-2.14), asn: 15169(-1.86), country: US(-0.05)]; FORGED_SENDER(0.30)[nomad@castle.org,thenomad@gmail.com]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[nomad@castle.org,thenomad@gmail.com]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jan 2020 00:02:24 -0000 I am (reluctantly) replacing am-utils (amd) with autofs. To do this I need to replace a lot of functionality that I've had embedded for a very long time and which my users absolutely rely on. I have two (so far) questions that I need to solve before I can proceed with this process. Question 1 - One of those features is the ability to use a symlink instead of a NFS mount. For a simplistic example: /homes/accountname -> /net/server/home/accountname On Linux this is a : entry in /etc/auto.homes: accountname :/net/server/home/accountname but when I test it on FBSD 11-3 I get: automountd[1784]: "mount -t nfs -o automounted,retrycnt=1 /net/[redacted]/vol/home/[redacted] /homes/[redacted]/", pid 1785, terminated with exit status 1 Which sure looks like it is trying to NFS mount the local filesystem, which clearly won't work. I use this functionality all over the place including linking into AFS space and making smart decisions of which subdirectory to present, so I can't just turn all of the links into NFS mounts. I found a bug report against the 10.1 version of autofs asking for the linking functionality but it was closed with no comment. I'm not finding any other documentation that references how to do a link. The media mount seems to be done via a special script instead of just a link. So, I have to ask, is this something that can be done? How do I do it? Question 2 - How do I get automount to reload a map if a filesystem is already mounted? It looks like issuing the "automount" command with no flags should get it to reload maps but it seems to be ignoring any changes to a map if that map has anything active. 99% of my map updates are to add a new filesystem to an existing map and I need all of the hosts to pick up the changes the next time CM runs. On Linux "systemctl reload autofs" does it but "service automount reload" doesn't exist, and as I said, "automount" ignores map changes for active maps. I'm _certain_ I'm missing something simple and obvious here, I can't believe there's no way to reload an active map. Any information related to either question is much appreciated. thanks nomad