On Wed, Jul 03, 2013 at 09:35:11PM -0700, patrick keshishian wrote: > Hi all, > > I installed 2013-JUN-27 snapshot and started building a bunch of > ports. I ran into this problem again on a few ports. See a snippet at > the end of this message. > > I *think* I have an idea of what may be going on to cause this issue, > but I'm not 100% certain. espie@ may have a better idea on this. > > I think this issue happened on all ports where my 'make install' > halted on an error, and was restarted. For example, if I started the > 'make install' on a biggish port (e.g., something that took hour+ to > build), where I walked away from the terminal, and eventually the > build process required me to enter a password for sudo, and sudo timed > out. > > I think the initial "lock" file remains in the $PORTSDIR/pobj/locks > directory, and when the build is restarted, > $PORTSDIR/infrastructure/bin/dolock gets stuck "Awaiting lock ...". > > I have not verified this, but it seems for the three ports I noticed > this, it was the case. > > Hope this is helpful in someway, > --patrick
Update /bin/sh.
