Escaping broke i 3.1.1 ?

[Tore Lønøy]

Let me see, this should be enough i think:

define host {
        host_name       X
        alias   X
        address X
        check_period    24x7
        check_command   check-host-alive
        contact_groups
        notification_period     24x7
        initial_state   o
        check_interval  15.000000
        retry_interval  5.000000
        max_check_attempts      3
        active_checks_enabled   1
        passive_checks_enabled  0
        obsess_over_host        1
        event_handler_enabled   0
        low_flap_threshold      0.000000
        high_flap_threshold     0.000000
        flap_detection_enabled  1
        flap_detection_options  o,d,u
        freshness_threshold     0
        check_freshness 0
        notification_options    d,r
        notifications_enabled   1
        notification_interval   60.000000
        first_notification_delay        60.000000
        stalking_options        n
        process_perf_data       1
        failure_prediction_enabled      1
        notes_url
        retain_status_information       1
        retain_nonstatus_information    1
        _REQUESTOR
        _CRM_SERVICES   "AOS$\$01"
        }

define service {
        host_name       X
        service_description     X
        check_period    24x7
        check_command   check_nrpe_parameters!CheckServiceState!ShowAll=long
$_HOSTCRM_SERVICES
        contact_groups
        notification_period     24x7
        initial_state   o
        check_interval  1.000000
        retry_interval  5.000000
        max_check_attempts      2
        is_volatile     0
        parallelize_check       1
        active_checks_enabled   1
        passive_checks_enabled  0
        obsess_over_service     0
        event_handler_enabled   0
        low_flap_threshold      0.000000
        high_flap_threshold     0.000000
        flap_detection_enabled  1
        flap_detection_options  o,w,u,c
        freshness_threshold     0
        check_freshness 0
        notification_options    c,r
        notifications_enabled   1
        notification_interval   60.000000
        first_notification_delay        10.000000
        stalking_options        n
        process_perf_data       0
        failure_prediction_enabled      1
        notes
        retain_status_information       1
        retain_nonstatus_information    1
        }

The problem for me it seems is when nagios is parsing the data just before
it is going to execute the command. It is no problem executes check_nrpe
with ah backslash (\) as the escape char. But the problem for me is what
escape char do i use in custom macros?

Best regards,

Tore

2009/6/23 Ton Voon <ton.voon at opsera.com>

>
>
> On 23 Jun 2009, at 10:12, Tore Lønøy wrote:
>
>  I just recently upgraded to the latest version, and now my escaping of '$'
>> is broken.
>>
>> Before it was \$, but what is it now?
>>
>
> Can you give a snippet of the configuration that is broken? Plus the
> appropriate parts of /usr/local/nagios/var/objects.cache
>
> As much real detail as possible will be good, though I understand you could
> have sensitive data there.
>
> Ton
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20090623/2ef892bb/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Are you an open source citizen? Join us for the Open Source Bridge conference!
Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250.
Need another reason to go? 24-hour hacker lounge. Register today!
http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null