[5.8-stable] some ports set locks then never release. The build can be induced 
to resume by manually removing the lock file. Nothing fancy - no concurrent 
builds - just a single port build, like math/R, will stop on a lock at least 
twice.

I imagine this is a known problem, but just in case I've done something 
peculiar...

drwxrwxr-x  53 root  wsrc   1536 Feb 15 02:45 ports/

/usr/ports fetched with CVS as a normal user in wsrc group. 
Builds are executed as a normal user in wsrc group.

$ cat /etc/mk.conf
SUDO=/usr/bin/doas
#COPTS="-march=native"
#CXXOPTS="-march=native"
CLEANDEPENDS=Yes

$ cat /etc/doas.conf
permit nopass keepenv { \
    FTPMODE PKG_CACHE PKG_PATH SM_PATH SSH_AUTH_SOCK \
    DESTDIR DISTDIR FETCH_CMD FLAVOR GROUP MAKE MAKECONF \
    MULTI_PACKAGES NOMAN OKAY_FILES OWNER PKG_DBDIR \
    PKG_DESTDIR PKG_TMPDIR PORTSDIR RELEASEDIR SHARED_ONLY \
    SUBPACKAGE WRKOBJDIR SUDO_PORT_V1 } :wsrc
permit nopass keepenv { ENV PS1 SSH_AUTH_SOCK } :wheel

$ userinfo hanzer
login   hanzer
passwd  *
uid     1000
groups  hanzer wheel wsrc
change  NEVER
class   staff
gecos   Adam Jensen
dir     /home/hanzer
shell   /bin/ksh
expire  NEVER

Reply via email to