Jump to content

CrazyC

Members
  • Content Count

    5
  • Joined

  • Last visited

  1. I have the pulseway daemon running on 3 different Macs. 2 are Mac Minis and 1 is a Mac Pro. The 2 Mac Minis have a steady flow of errors like this in their logs: Mar 30 20:23:52 ny2 kernel[0]: SMC::smcReadKeyAction ERROR TN0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80220d2000 Mar 30 20:23:52 ny2 kernel[0]: SMC::smcReadKeyAction ERROR TB0T kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80220d2000 Mar 30 20:23:52 ny2 kernel[0]: SMC::smcReadKeyAction ERROR F1Ac kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80220d2000 Mar 30 20:23:57 ny2 kernel[0]: SMC::smcReadKeyAction ERRO
  2. Hmm, ok. I will restated my comment about it just doesn't seem fair that Mac Admins are charged the same rate as Windows admins with less than 1/2 the features. This is my only hang up at this point. Some how, I don't see getting a break for that, but it would certainly be a nice thought, maybe even for the first year since there are so many things not available for Macs at the present.
  3. I've been testing Pulseway out for a few weeks now and have about 2 weeks before my trial expires. So far, I really like Pulseway and what it does, but I'm very concerned that there are tons of features for monitioring windows servers and there's quite a bit that can be configured for linux (I haven't dug into this yet), but the OS X daemon seems to be lacking in features. Why can't we monitoring services on Macs? I don't see services or scheduled tasks for Macs. For Mac servers (using Apple's server app) I would think it should be pretty simple to integrate with status off the se
×
×
  • Create New...