I just got this and I don't know why. Never seen it. I thought the key I set up was never expire.
cpu% auth/secstore -g factotum secstore password: auth/secstore: error: account expired I'm too dumb to figure the way out. Sorry. So, how do you dig yourself out of this hole? I can just fix the code to disable that test, surely there is something better to do here. This is also another "useless message" example that drives part time guys like me nuts. Would it really absolutely run counter to all Plan 9 principles, and violate peoples lives, fortunes, and sacred honor, to PRINT THE FRIGGING DATES? It would at least tell me, if the dates were totally nuts, that there was corruption going on here. This message contains (almost) not useful data. Just wondering. thanks ron
