Wednesday, 4 May 2005
Meet securityd… or don’t.
Back in Mac OS X 10.0 and 10.1, the bane of my existence was lookupd dying and hanging the machine impossibly. In Tiger, a similar culprit appears to be securityd.
root 43 0.0 0.2 29332 3632 ?? Ss 8:42PM 0:00.43 /usr/sbin/securityd
Innocent-looking, isn’t it? But when it dies, don’t expect to be able to launch graphical processes, or restart cleanly, or sudo… and it’s died four times in the past week, necessitating the repeated use of the triangle-logoed button on the front of my G4.
1:48 AM | PyCS
