[Xymon] Client install gone wrong
Diep, David (OCTO-Contractor)
David.Diep at dc.gov
Tue Dec 17 13:46:39 CET 2013
I just assumed that was the proper way of setting up Xymon. One machine playing the role of the central server while the others are the clients. I noticed that the server does utilize more CPU cycles, in my case they share CPU resources.
I will do the server side configuration instead.
From: Jeremy Laidman [mailto:jlaidman at rebel-it.com.au]
Sent: Monday, December 16, 2013 9:38 PM
To: Diep, David (OCTO-Contractor)
Cc: xymon at xymon.com
Subject: Re: [Xymon] Client install gone wrong
On 17 December 2013 06:36, Diep, David (OCTO-Contractor) <David.Diep at dc.gov<mailto:David.Diep at dc.gov>> wrote:
CC="gcc" CFLAGS="-g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I`pwd`/include -DCLIENTONLY=1 -DLOCALCLIENT=1
Any reason why you opted for client-side configuration instead of the (default) server-side aka central mode? I think if you build it with server-side config, it will work.
The reason it's failing is there seems to be a bug in the makefile creation that sets PCREINCDIR to "-l" instead of a valid directory or empty. You can probably get further with this:
$ make PCREINCDIR=""
But there seems to be other problems. So I'd recommend using server-side configuration.
Look out for those in need this winter. When the temperature or wind chill is 32?F or below, the District issues a Hypothermia Alert. For assistance during an Alert, call the Shelter Hotline<http://dhs.dc.gov/page/hypothermia-alert-plan> at 1-800-535-7252 or 311.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Xymon