On 07/06/2011 02:15 AM, Ryan Schmidt wrote: > And I'm not convinced setting it to /var/empty is a great solution. > The issue in response to which you changed it from /dev/null to > /var/empty was about a program's inability to create some sort of > directory in home for its settings. So now it's going to create that > settings directory inside /var/empty, which seems wrong; that > directory *should* remain empty. I don't know if the OS cleans it out > at some point.
The user 'macports' will not have write access to /var/empty and thus cannot create any files there. Rainer _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
