Dating from back when I was building ports on each of the 3 machines on one of my networks using portmaster(8), I have had my ports tree implemented as an SVN working copy that resides on a ReadyNAS, which is thus accessed via NFS.
The 3 machines are running "recent" FreEBSD stable/10 (amd64): the build
machine is updated daily, and is thus updated to r293654; the other 2
machines are only updated weekly, so they are presently updated to
r293620.
A couple of the machines use autofs & automountd to make the ports tree
available on demand. (In the case of the 3rd, I manually mount it when
needed, but that's not at issue for this note, and I won't pursue that
further here.)
The machines that use autofs do so by using symlinks and the existing
maps; e.g.:
albert(10.2-S)[7] ls -lT /usr/ports
lrwxr-xr-x 1 root wheel 20 Dec 21 04:15:39 2010 /usr/ports ->
/net/howland/c/ports
albert(10.2-S)[8] cat -n auto_master
1 # $FreeBSD: stable/10/etc/auto_master 283242 2015-05-21 13:42:37Z trasz
$
2 #
3 # Automounter master map, see auto_master(5) for details.
4 #
5 /net -hosts -nosuid,intr
6 # When using the -media special map, make sure to edit devd.conf(5)
7 # to move the call to "automount -c" out of the comments section.
8 #/media -media -nosuid
9 #/- -noauto
albert(10.2-S)[9]
The contents of /etc/autofs are "vanilla" -- I have not changed
them. I did modify /etc/auto_master a bit, to remove the "nobrowse"
option for -net.
For most purposes, including:
* svn update
* cd to a port directory
* Updating files in distfiles
* reading arbitrary files in the tree
this works well, and there's no indication of any problems or issues.
I recently noticed, thiough, that running "portmaster -aF" generates a
large number of messages.
I was able to narrow this down to portmaster's invocation of (e.g.)
* cd /usr/ports/sysutils/dmidecode
* make -V PKGNAME
The "cd" seems OK; it's the "make -V PKGNAME" -- even if I invoke it by:
hand. It works, but at the expense of messages:
albert(10.2-S)[4] dirs; date; make -V PKGNAME; date
/usr/ports/sysutils/dmidecode
Mon Jan 11 07:26:45 PST 2016
dmidecode-3.0
Mon Jan 11 07:26:47 PST 2016
albert(10.2-S)[5]
Jan 11 15:26:45 albert automountd[13912]: "/etc/autofs/special_hosts share",
pid 13913, terminated with exit status 1
Jan 11 15:26:45 albert automountd[13912]: failed to handle special map "-hosts"
Jan 11 15:26:45 albert kernel: WARNING: autofs_trigger_one: request for /net/
completed with error 5
Jan 11 15:26:46 albert automountd[13915]: "/etc/autofs/special_hosts share",
pid 13916, terminated with exit status 1
Jan 11 15:26:46 albert automountd[13915]: failed to handle special map "-hosts"
Jan 11 15:26:46 albert kernel: WARNING: autofs_trigger_one: request for /net/
completed with error 5
Jan 11 15:26:47 albert automountd[13918]: "/etc/autofs/special_hosts share",
pid 13919, terminated with exit status 1
Jan 11 15:26:47 albert automountd[13918]: failed to handle special map "-hosts"
Jan 11 15:26:47 albert kernel: WARNING: autofs_trigger_one: request for /net/
completed with error 5
So I'm wondering why make(1) appears to be doing something that
causes this -- while nothing else (that I've noticed so far) does.
Peace,
david
--
David H. Wolfskill da...@catwhisker.org
Those who would murder in the name of God or prophet are blasphemous cowards.
See http://www.catwhisker.org/~david/publickey.gpg for my public key.
signature.asc
Description: PGP signature
