Hi, On Tue, Feb 04, 2025 at 09:38:07AM -0300, Gregorio Litenstein wrote: > Hey all. I was about to post a ticket, but honestly this is probably > just a me problem. In fact, it's not even really a problem; more of an > annoyance, really. > > […] Just one gripe I have is that sometimes, I can't eject the disk > cleanly because secd (invoked by the macports user) is has the > keychain at `/opt/local/var/macports/home/Library/Keychains/` > permanently open. Of course, I can kill that instance of secd (My > usual workaround) but I was wondering, a) What is on that keychain, > and b) Whether it might be possible to change something in the way > macports talks to secd so this doesn't happen?
MacPorts doesn't talk to secd; it's very likely some tool used by the build process in a port you have built that triggers the creation of this directory. I actually also have one on my installation. You can check whether yours has any contents, since the database is just sqlite3: $> sudo sh -c 'sqlite3 /opt/local/var/macports/home/Library/Keychains/*/*.db ".dump"' | grep ^INSERT On my system, this only prints two lines that record the version of the database schema, but no contents. In fact, you should be able to delete all contents of `/opt/local/var/macports/home` without side effects. It seems most (or all) of the data in there is created by Xcode. HTH, Clemens
