I just came across the quirkiest Solaris bug.. I installed Cricket today to monitor and graph, well.. just about anything.
Anyway, the Cricket collector runs from a cron job. I had followed all the instructions to a T, set up a new Cricket user, and all software seemed to have been installed fine and would run fine by hand. I set up the cronjob and been waiting for data to come in.. nothing. I have re-read the README and poked around in all the config files and directories - still nothing. Finally i came around to thinking about cron. Checked for the daemon, yeah it was running fine so i restarted it. nothing. I added another cronjob to the Cricket user to just email me, which i had verified worked from the command line. no email. Finally i got around to checking the /var/cron/log file, which i should have done earlier, but, well, you know how it is! And found this line: ! bad user (cricket) Thu Feb 3 17:25:00 2005 A quick google later tells me this was a bug (or feature) introduced in Solaris 8, whereby if the users account has no password, or is locked out, then his/her cronjobs wont run and it gives you this message. One passwd later and its all fine. d'oh. thor -----------------------------------------------------------------------| Highpoint Lowlife Records http://www.highpointlowlife.com/ bitmapped indie-electronic goodness since '01 ------------------------| -----------------------------------------------------------------------| _______________________________________________ Bits mailing list [email protected] http://www.sugoi.org/mailman/listinfo/bits
