Where is development going on in SVN?
I have been using xymon compiled from about 6+ months ago. I have used the old "hobbitmon" project. I found some issues with the 4.2 version and tried branches/4.3.0 and branches/4.4.0. It looked like 4.3 and 4.4 were mostly the same so I went with 4.4.0.
I found that I needed to patch quite a few files to get things working right. This was all prior to the hobbit->xymon changes.
Now I was asked to setup another monitoring server and thought I would try out the new project.
I was looking at the SVN to see if anything I had to patch was fixed but I am confused as to where to look for the latest revisions.
Looking at the last few commits it looks like they have been going into "trunk". Looking at revisions it looks like branches/4.4.0 is newer than trunk.
So what is the development area? "trunk" or "branches"?
I want to also see if the patches I created are still needed and if so then would like to somehow get them into the repo.
Thanks
On Friday, 3 September 2010 16:07:30 Cade Robinson wrote:
I have been using xymon compiled from about 6+ months ago. I have used the old "hobbitmon" project.
Which version?
I found some issues with the 4.2 version and tried branches/4.3.0 and branches/4.4.0.
There were quite a few bugfixes in 4.2.3, the first version released as xymon. While 4.3.0 has received some bugfixes that may not be in a released version of 4.3.x, there are still some known bugs that are present in 4.3.0 that are not present in any 4.2.x release ...
It looked like 4.3 and 4.4 were mostly the same so I went with 4.4.0.
I found that I needed to patch quite a few files to get things working right. This was all prior to the hobbit->xymon changes.
Now I was asked to setup another monitoring server and thought I would try out the new project.
I was looking at the SVN to see if anything I had to patch was fixed but I am confused as to where to look for the latest revisions.
Looking at the last few commits it looks like they have been going into "trunk".
I think the majority of commits to trunk and 4.4.0 were forward-porting from 4.3.0.
Looking at revisions it looks like branches/4.4.0 is newer than trunk.
I think this is largely artificial.
So what is the development area? "trunk" or "branches"?
Well, that depends. New features will probably go to trunk (some minor ones may still go to 4.3.0, but we need to try and finalise the features for 4.3.0 so we can get a new beta out). Bugfixes from testing 4.3.0 beta or svn will go to 4.3.0, and forward-ported if appropriate.
I want to also see if the patches I created are still needed and if so then would like to somehow get them into the repo.
I don't think anyone is actively developing on 4.4.0 at present, so I think target 4.3.0 and we will forward port as appropriate.
Regards, Buchan
In <4c810f34.1336640a.7534.6383 at mx.google.com> "Cade Robinson" <cade.robinson at gmail.com> writes:
Looking at the last few commits it looks like they have been going into "trunk". Looking at revisions it looks like branches/4.4.0 is newer than trunk.
So what is the development area? "trunk" or "branches"?
Not surprising you are confused, it is somewhat messy right now.
Development right now happens in the "branches/4.3.0" area.
"trunk" got really messy because I was trying to juggle multiple development paths simultaneously (due to urgent requirements for functionality). So that is "on hold" right now, and once 4.3.0 is ready we will probably just dump it into trunk and take development from there.
"4.4.0" is very experimental (some SNMP stuff there, but don't use it). I think that branch will be killed when 4.3.0 is out. The good stuff from 4.4.0 has been merged into 4.3.0 development, all except the SNMP stuff.
Regards, Henrik
On 09/23/2010 09:03 AM, Henrik Størner wrote:
"4.4.0" is very experimental (some SNMP stuff there, but don't use it). I think that branch will be killed when 4.3.0 is out. The good stuff from 4.4.0 has been merged into 4.3.0 development, all except the SNMP stuff.
Is that SNMP stuff going to be scrapped all together, or will a future release of xymon have it (once it gets fixed)?
Tom
In <4C9B5229.2040704 at mcclatchyinteractive.com> Tom Georgoulias <tomg at mcclatchyinteractive.com> writes:
On 09/23/2010 09:03 AM, Henrik St�rner wrote:
"4.4.0" is very experimental (some SNMP stuff there, but don't use it). I think that branch will be killed when 4.3.0 is out. The good stuff from 4.4.0 has been merged into 4.3.0 development, all except the SNMP stuff.
Is that SNMP stuff going to be scrapped all together, or will a future release of xymon have it (once it gets fixed)?
It will show up somewhere / sometime. The main problem I have with it is that it doesn't scale to the size of the switches we have to monitor - the amount of data the current code tries to push into the hobbitd daemon is just too great (consider the issue of a 1000-port switch where you want full SNMP interface statistics for all ports...)
So I need to do some rethinking of how exactly that should work.
Regards, Henrik
I have this problem, using Page directive in hobbitdboard .. i'm using hobbit 4.2.0 .. In the version 4.2.3 is resolved ? regards Marco
Il 19/12/2008 9.53, Henrik Størner ha scritto:
In<A3D12FAD74FC8B46991703F40C182BABAB467086 at permls102.wde.woodside.com.au> "Everett, Vernon"<Vernon.Everett at woodside.com.au> writes:
Please correct me if I am wrong, but if in bb-hosts, I have
page prod Production Servers group Unix Production 0.0.0.0 server1 # 0.0.0.0 server2 # 0.0.0.0 server3 # page test Test Servers group Unix Test 0.0.0.0 server4 # 0.0.0.0 server5 # 0.0.0.0 server6 # page oracle Oracle Servers group Oracle Production 0.0.0.0 server3 # noconn Group Oracle Test 0.0.0.0 server6 # noconn 0.0.0.0 server7 #
And in a config file I use PAGE=3Dprod, it should limit itself to server1, = server2 and server3.
However PAGE=3Doracle doesn't seem to pick up the server3 and server6. But it does seem to apply to server7
The problem is that you have servers on multiple pages. The "PAGE=..." setting in 4.2.x only matches against a single page where the server is located (on the "info" status page, I believe it's the location that is listed first. So it won't pick up your server3 and server6 as being on the "oracle" page.
This has been changed for 4.3.0.
There's no "SUBPAGE=...", by the way - the "PAGE=..." works on the page path - i.e. if you have page prod subpage web 0.0.0.0 webserver1 page test subpage web 0.0.0.0 testserver1
then the full PAGE for webserver1 would be "prod/web" . A "PAGE=web" would match this, but would also match "testserver1" because it's on a "web" subpage (path for that is "test/web".
"PAGE=..." supports regular expressions.
Regards, Henrik
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
Now I know what to use for "bleeding edge".
I do have some patches I would like to submit for 4.3.0. I am no C coder and have just hacked my way through but I have a fix for at least 5 issues that affected me.
Who can those go to for review?
Looking at the last few commits it looks like they have been going into "trunk". Looking at revisions it looks like branches/4.4.0 is newer than trunk.
So what is the development area? "trunk" or "branches"?
Not surprising you are confused, it is somewhat messy right now.
Development right now happens in the "branches/4.3.0" area.
"trunk" got really messy because I was trying to juggle multiple development paths simultaneously (due to urgent requirements for functionality). So that is "on hold" right now, and once 4.3.0 is ready we will probably just dump it into trunk and take development from there.
"4.4.0" is very experimental (some SNMP stuff there, but don't use it). I think that branch will be killed when 4.3.0 is out. The good stuff from 4.4.0 has been merged into 4.3.0 development, all except the SNMP stuff.
Regards, Henrik
On 09/23/2010 03:28 PM, Cade Robinson wrote:
Now I know what to use for "bleeding edge".
I do have some patches I would like to submit for 4.3.0. I am no C coder and have just hacked my way through but I have a fix for at least 5 issues that affected me.
Who can those go to for review?
At the very least, you could send them to the xymon-developer list, xymon-developer at lists.sourceforge.net
Others have contributed patches in the same manner.
Tom
participants (5)
-
bgmilne＠staff.telkomsa.net
-
cade.robinson＠gmail.com
-
henrik＠hswn.dk
-
marco.avvisano＠regione.toscana.it
-
tomg＠mcclatchyinteractive.com