This bug was recently discovered and a patch has been created (search
the Nagios-Devel mailing list). The patch changes the mime type to
audo/x-wav and does one other thing that makes everything groovy in
Firefox and in IE. I can't say for sure, but I'd expect this to be fixed
in a future release of Nagios if you're not willing to patch and
recompile. 

 

-Jake

 

________________________________

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of J.VC
Sent: Thursday, July 24, 2008 8:58 AM
To: nagios-users@lists.sourceforge.net
Subject: [Nagios-users] Nagios V3, no sound in webbrowsers.

 

Hi!

 

I don't hear any sound alerts whenever there is something wrong. I've
figured out that Nagios v3 runs the mime-type application/wav, thats not
supported by webbrowsers. That used to be application/x-mplayer2, which
is supported by many browsers.

 

To change that i need to edit status.cgi and tac.cgi. Here's the thing.
I've never edited an sourcecode or compiled something like this. Anyone
out there who can help me out on this one?

 

Current workaround: i've installed a add-on in FireFox,
http://code.google.com/p/nagioschecker/
<wlmailhtml:%7b65FA0935-1AB9-45CC-B8D3-6CC8D640FEB4%7dmid://00000021/!x-
usc:http://code.google.com/p/nagioschecker/>  that's working great. But
i'd still like to have the original page playing the sounds.

 

Thank you in advantage.

 

Uc

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Nagios-users mailing list
Nagios-users@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

Reply via email to