NetXMS Support Forum

Hello!

I've fixed that. You can try to install 1.1.0-rc11 - https://www.netxms.org/download/agent_packages/nxagent-1.1.0-rc11-x64.exe.

Best regards,
Victor

Yes, it will work under WINE.

GUI pod Linux poka net. Mi sejchas pishem novij portabel'nij GUI (ja cherez neskol'ko dnej vilozu preview), no projdet nekotoroe vremja, poka pojavjatsja vse funkcii starogo GUI. Nineshnij GUI napisan pod Windows s ispol'zovaniem MFC, tak chto sportit' ego vrjad-li udastsja. On rabotaet pod WINE, no eto konechno ne sovsem to.

A parametr Disk.Total(D:) sobiraetsja?

There are currently no management console for Linux. We are working on new portable management console (I'll publish a preview in a few days), but it will take some time until all functionality of existing Widnows console will be implemented.

Best regards,
Victor

Hi!

Quote from: jdl on March 10, 2010, 07:19:21 PM
- When creating a node, reverse lookup would be interesting. Sometimes one knows the IP but not the FQDN. If you enter an IP @ and push "resolve" you get IP @ of localhost (the one running the console) and no name.

Currently, you can enter IP address as node name, press "Resolve" to fill IP address field with same value. If node has IP address as it's name, it will be resolved via DNS or agent at first configuration poll. But yes, reverse lookup in dialog could be useful.

Quote from: jdl on March 10, 2010, 07:19:21 PM
- when defining a new event processing rule, we hav eto close the window to get asked if we want to save the story. Would be nice to have a drop down menu with options (like duplicate rule, etc...) among which "save" to save the current config if relevant (if no change then greyed out ;-)

You can use main menu Policy -> Save policy or just press Ctrl+S.

Best regards,
Victor

Hi!

In NXSL, you can use any integer value as boolean, where 0 means false and any-non-zero value means true. So, you can use errorCount attribute as boolean flag if you wish, like below:

if (dci->errorCount)
{
    // Processing if error
}
else
{
   // Processing if OK
}

You can also apply boolean logic operations to integer values, for example:

if (!dci->errorCount)
{
   // Processing if there are no errors
}


Best regards,
Victor

Hi!

I'll post updated NetXMS User Manual in a few days - it will have chapter about NXSL programming.

Best regards,
Victor

A kak vigljadit parametr Disk.Total i chto propisano v pole "instance" dlja parametra so skriptom? Problema pohoze v tom, chto formiruetsja nepravil'noe imja parametra, i FindDCIByName vozvraschaet NULL.

Hi all!

Vesrion 1.0.0-rc2 is out. It fixes some build problems found in rc1, and adds possibility to search objects by comments in Windows console.

Best regards,
Victor

Ja ispravil odin bag v configure i perepakoval 1.0.0-rc2 (https://www.netxms.org/download/netxms-1.0.0-rc2.tar.gz) - poprobujte novij variant.

Hi!

Yes, you can call library script from another library script in a same way.

I'll check script saving in MS SQL a bit later.

Best regards,
Victor

Hello!

It's very strange - there are no size limitation on scripts. What database you are using?

To call one script from another, called script must be in script library, and contain function(s) other than main(). Then in calling script you should add use statement, for example:

script in library, called my_script:


sub my_function()
{
   return "some value";
}


script in event processing policy:


use my_script;

sub main()
{
   value = my_function();
   // some further processing
}


Best regards,
Victor

Please try 1.0.0-rc2 (https://www.netxms.org/download/netxms-1.0.0-rc2.tar.gz) - this problem should be fixed.

Best regards,
Victor

It will require changes in very important part of code, and in turn will require additional tests - and I wouldn't want to do this until 1.0.0 release. However, I have added new attribute to DCI object - errorCount - which you can use to check from NXSL if given DCI had data collection error. This attribute will be 0 if last poll was completed succesfully, or > 0 if there was an error (will hold number of consecutive data collection errors).

Best regards,
Victor