If portmanager is run as a user other than root it dumps core because the user does not have write perms for /usr/local/share/portmanager/ignore.db. This is not very graceful! /home/mark{4}% portmanager touch: /usr/local/share/portmanager/ignore.db: Permission denied MGdbCreate error, lstat of /usr/local/share/portmanager/ignore.db failed lstat: No such file or directory Assertion failed: (0), function MGdbCreate, file MGdbCreate.c, line 64. Abort (core dumped) /home/mark{5}% Fix: Apply the following patch How-To-Repeat: Run portmanager as a non-root user
State Changed From-To: open->feedback Wouldn't it be better to check permissions on that file and bail out only when the permissions are not met?
Responsible Changed From-To: freebsd-ports-bugs->pav Track
I thought about that, but since you need to be root to use the ports system it seems to make sense to only allow portmanager to run as root.
State Changed From-To: feedback->open Feedback received
State Changed From-To: open->closed Committed, thanks!