Xymon now available on Mac OS X 🔗 link

Dear Xymon enthusiasts,


I'm pleased to announce Xymon is now available on Mac OS X throught the macports.org project:
http://www.macports.org/ports.php?by=name&substr=xymon

You'll find install instructions for xymon server here:
https://trac.macports.org/wiki/howto/SetupXymonServer


This port is based on the latest 4.3.0.beta3 code which implements the new names for config files and variables.

I successfully tested it on Snow Leopard 10.6.5 and Snow Leopard Server 10.6.5. There's only one problem identified so far which is a huge CPU load by "showgraph.cgi" while generating the graphs -> any help is welcome to identify the root cause.


Cheers,
Francois.

Great Show !

Congratulations, Francois :-)

One question:

Is it possible to install only the client ?


cheers,
 	martin

On Wed, 24 Nov 2010, Francois Claire wrote:

Hi Martin,


Yes, install the client with "sudo port install xymon".

And the server (including the client) with "sudo port install xymon-server".


The 2 ports conflicts each other so only one of the 2 should be installed on a single machine.


Cheers,
Francois.

Le 24/11/10 09:41, Martin Flemming a écrit :

On Wednesday, 24 November 2010 10:13:25 Francois Claire wrote:

I note that packaging of Xymon for other operating systems usually takes the other route, 'xymon-client' for the client part, and 'xymon' for the server (either including the client bits or depending on xymon-client).

If there are no differences either way, it might be better to provide be consistent for users across platforms.

BTW., we any patches required (so far)? If so, please submit them.

Regards,
Buchan

Hi Buchan,

Indeed but in macports it looks like the port names have a "-server" suffix for server part:
mysql5 and mysql5-server : http://www.macports.org/ports.php?by=name&substr=mysql5
clamav and clamav-server : http://www.macports.org/ports.php?by=name&substr=clamav

...

You're right it might be better to have consistent naming across platforms but changing the name has an impact on the port file. Feel free to propose a Portfile patch to the macports community (documentation is here: http://guide.macports.org/#project.update-policies).

I don't have commit privileges so you'll need to create a trac ticket (http://guide.macports.org/#project.tickets) to get your changes accepted by the macports commiters.

BTW., we any patches required (so far)? If so, please submit them.

I've submitted 3 patchs the 16th Nov in the Xymon-developer mailing list.

Regards,
Buchan

Regards,
Francois.

On Wed, Nov 24, 2010 at 10:36 AM, Francois Claire <user-4b143d727ceb@xymon.invalid> wrote:

Maybe the ports could be named xymon-server and xymon-client, for
minimum ambiguity.  Then "xymon" can be either nonexistent (forcing
the would-be installer to notice the real names) or even just print
out a warning/readme.txt.

Just a thought.  I have no idea if this is functional.

Jaime

-- 
Network Administrator
Cairo-Durham Central School District
http://cns.cairodurham.org

Hi Jaime,

Buchan said it might be better to have consistent naming across platforms. Your proposal of using "xymon-server" and "xymon-client" might also apply to other packages than the MacPorts. So RPMs and debian packages might be adapted as well.


I don't care about the names of the packages as long as there's some documentation to guide the users. In the case of the macports it is specified which port is the client/server part on the wiki page:
https://trac.macports.org/wiki/howto/SetupXymonServer

And Mac users can search for xymon ports with the following command:

$ port search xymon
xymon @4.3.0.beta3 (net)
     Xymon network monitor Client

xymon-server @4.3.0-beta2 (net)
     Xymon network monitor Server

Found 2 ports.
$

Which clearly identifies which one is the client and which one the server.


As said before I don't care about the names of the packages and therefore I don't see a problem if they change. The only thing is that it shouldn't create myself more work. This is why I propose to people willing to change the names to propose their own Portfile patch (documentation is here: http://guide.macports.org/#project.update-policies) and submit it to the macports community. Even being the maintainer, I don't have commit privileges so you'll need to create a trac ticket (http://guide.macports.org/#project.tickets) to get your changes accepted by the macports commiters.


Regards,
Francois.