That got it; I didn't have startup=automatic as part of that entry.

Granted it's fairly pointless, but it serves both as a test of that functionality, and as something so the column is green rather than clear. :-) I don't think I have any other extra services of interest on there (notwithstanding stuff like Google Update Service).

On Tue, Jan 31, 2017 at 7:45 PM, Brandon Dale <BDale at kitchengroup.com.au> wrote:

I would assume it’s just putting this into the analysis.cfg file for the host you want to monitor:

SVC XymonPSClient status=started startup=automatic

However… not sure that will do anything useful? If the service stops it will never send the data to the xymon server so the alert would never trigger, not for the status anyway. As long as you have alerting setup for stuff going purple then you should be fine.

Regards,

*Brandon *

*From:* Xymon [mailto:xymon-bounces at xymon.com] *On Behalf Of *Richard Hamilton *Sent:* Wednesday, 1 February 2017 11:27 AM *To:* Alessandro Tinivelli <Alessandro.Tinivelli at faacgroup.com> *Cc:* xymon at xymon.com *Subject:* Re: [Xymon] [EXCH Prio5]R: [EXCH Prio5]Re: linux client disk warning levels

For those wishing to switch, here's my notes on uninstalling BBWin, since I didn't find any. All this assumes one is using the Administrator account, or at least an account with Administrator privileges. Also, if you use zip somewhere else to package up the WinPSClient files, do NOT use cygwin's unzip to extract them; it will get some Windows permissions wrong, and nssm (if not more) won't work properly. Aside from that, I haven't figured out how to use the svcs test to detect that the XymonPSClient service is running; maybe I can change it to check for nssm, or have procs check for nssm. But otherwise, WinPSClient seems to be working as well or better as BBWin did on Windows 8, at least on the Windows 10.1 VM on my Mac laptop.

To remove BBWin:

Stop the BBWin service (may be named Big Brother Xymon Client) using the

usual service management GUI.

Remove the service; from command line: sc delete BBWin

Once that's done, some quick regedit searches seem to show no leftovers in

the registry.

Remove the software; from the command line: rd/s "Program Files (x86)\BBWin"

On Tue, Jan 31, 2017 at 2:56 AM, Alessandro Tinivelli < Alessandro.Tinivelli at faacgroup.com> wrote:

Hi Kris,

believe me, it’s always better to write settings on server side instead of client side.

And, for windows clients, I strongly suggest you to switch to the Zak’s great powershell client, you can get out from svn

"svn checkout http://svn.code.sf.net/p/xymon/code/sandbox/WinPSClient ."

This behaves more like a linux client, and that’s cool

Alessandro

*Da:* Xymon [mailto:xymon-bounces at xymon.com] *Per conto di *Kris Springer

Understood about the server doing the deciphering of the client data. Strange that the Windows clients are easily adjusted on the client end.

I don't have an analysis.d folder. I think I'll just add the custom levels into the analysis.cfg file and see what happens.

---

Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon