NetXMS Forum

OK,that definitely helps.  Thanks again.

Tony

@victor said in Licensing:

Version 1.0.5 just released, where I have changed licensing for most libraries to LGPL. Current licensing scheme is as follows:

Thanks Victor!  My only remaining concern is with subagents.  Does the GPL licensing of nxagentd and all the subagents mean that a custom subagent cannot be developed without releasing it as GPL?  (I'm still working on getting a build environment configured and do not yet know the dependencies of a subagent, but I assume it would have to link against nxagentd).  Thanks.

Tony

I'm seeing the same thing on 1.0.4.

Tony

Great!  Thank you very much!

Thanks very much, that's the answer I was hoping to get.  Do you have any plans to put anything to that effect in writing?  My employer takes license compliance very seriously, so if the only license put forth in writing is GPL, and my proposed use will violate that license, they'll never let me do it, even with your assurance above.  Thanks.

Tony

Hi.  I have a quick question for the developers about licensing.  I noticed that NetXMS is under GPL v2.0.  (Just a tip, there should be a place to find this out on the homepage without having to download the source code).

I was wondering whether you have, or would, consider releasing any portion of NetXMS under LGPL.

To clarify, LGPL is the Lesser GPL, and in a nutshell it says that you can build your own custom code (a derivative work) against a library released under the LGPL license without having to release your custom code as GPL.

I am interested in recommending your software to a customer.  NetXMS meets most, but not all, of my customer's requirements and I would be tasked to write some custom software, probably linking against your API, to fill in the missing functionality.  But I'm quite certain that my customer would not consent to releasing the code I develop for them as open source.  LGPL was intended to address just this sort of situation.

Anyway, there are a wide range of attitudes on whether FOSS should be able to be used to build commercial software or not, and I was wondering whether the lack of mention of LGPL was inadvertent or intentional.  Thanks.

Tony

@victor said in Status Return Codes for Windows Services:

It' an internal parameter (i.e. it represents information existing inside NetXMS server, not on target node). Internal parameter Status represents current node's status in NetXMS encoded as follows:

0 = Normal
1 = Warning
2 = Minor
3 = Major
4 = Critical
5 = Unknown
6 = Unmanaged

There also internal parameter ChildStatus(), which represents status of given node's child object. In addition to status codes listed above, interface objects can have the following additional status codes:

7 = Disabled
8 = Testing

Best regards,
Victor

I've noticed that I get status 4 when I unplug a network cable to a managed object.  I was wondering if there is any other condition other than not being able to communicate with an object (because it's unplugged, or turned off) that can lead to a status of "critical".  IE if I see this status, can I safely assume that my server cannot talk to the managed device?

Thanks.

Tony