Page 1 of 1

[Nagios-devel] Re: patch: spelling cleanup

Posted: Mon Nov 01, 2004 10:25 pm
by Guest
--=-1KGF53itaJaCeoBZ1OqU
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

On Mon, 2004-11-01 at 23:20, Matthew Kent wrote:
> Here's an exciting one. Ran http://www.kegel.com/kerspell/ against the
> source to find some spelling mistakes in comments. Also found a number
> in html outputs too.
>
> Patch against latest cvs.

Oops, accidentally included the other patch I just sent in. Just the
spellcheck this time!

--
Matthew Kent
http://magoazul.com

--=-1KGF53itaJaCeoBZ1OqU
Content-Disposition: attachment; filename=nagios-2.0a1-spellcheck2.patch
Content-Type: text/x-patch; name=nagios-2.0a1-spellcheck2.patch; charset=ANSI_X3.4-1968
Content-Transfer-Encoding: 7bit

diff -u3 -r nagios_orig/base/checks.c nagios/base/checks.c
--- nagios_orig/base/checks.c 2004-11-02 04:19:04.000000000 +0000
+++ nagios/base/checks.c 2004-11-02 04:19:16.000000000 +0000
@@ -284,7 +284,7 @@
else
args[3]=processed_command+strlen(fname)+1;

- /* reinialize embedded perl if necessary */
+ /* reintialize embedded perl if necessary */
if(use_embedded_perl==TRUE && max_embedded_perl_calls>0 && embedded_perl_calls>max_embedded_perl_calls)
reinit_embedded_perl();

@@ -358,7 +358,7 @@
perl_plugin_output = SvPOK(plugin_out_sv) && (SvCUR(plugin_out_sv) > 0) ? savepv(SvPVX(plugin_out_sv))
: savepv("(No output!)\n") ;
strncpy(plugin_output, perl_plugin_output, sizeof(plugin_output));
- /* The Perl scalar corresp to pclose_result could contain string or integer.
+ /* The Perl scalar corresponding to pclose_result could contain string or integer.
It is better to let POPi do the dirty work (SvPVOK or SvIOK could be true).
*/
pclose_result = POPi ;
@@ -787,7 +787,7 @@
verify_route_to_host(temp_host,CHECK_OPTION_NONE);

#ifdef REMOVED_080303
- /* really check the host status if we're using agressive host checking */
+ /* really check the host status if we're using aggressive host checking */
if(use_aggressive_host_checking==TRUE)
verify_route_to_host(temp_host,CHECK_OPTION_NONE);

@@ -888,7 +888,7 @@
temp_service->last_notification=(time_t)0;
temp_service->next_notification=(time_t)0;

- /* reset notification supression option */
+ /* reset notification suppression option */
temp_service->no_more_notifications=FALSE;

if(temp_service->acknowledgement_type==ACKNOWLEDGEMENT_NORMAL){
@@ -993,7 +993,7 @@
handle_service_event(temp_service);
}

- /* else no service state change has occured... */
+ /* else no service state change has occurred... */

/* should we obsessive over service checks? */
if(obsess_over_services==TRUE)
@@ -1026,7 +1026,7 @@
/******* SERVICE CHECK PROBLEM LOGIC *******/
/*******************************************/

- /* hey, something's not working quite like it should... */
+ /* hey, something isn't working quite like it should... */
else{

#ifdef DEBUG_CHECKS
@@ -1053,7 +1053,7 @@
printf("\tSECTION B2a\n");
#endif

- /* we're using agressive host checking, so really do recheck the host... */
+ /* we're using aggressive host checking, so really do recheck the host... */
if(use_aggressive_host_checking==TRUE){
route_result=verify_route_to_host(temp_host,CHECK_OPTION_NONE);
#ifdef DEBUG_CHECKS
@@ -1104,7 +1104,7 @@
printf("\tSECTION B3\n");
#endif

- /* "fake" a hard state change for the service - well, its not really fake, but it didn't get caught earler... */
+ /* "fake" a hard state change for the service - well, its not really fake, but it didn't get caught earlier... */
if(temp_service->last_hard_state!=temp_service->current_state)
hard_state_change=TRUE;

@@ -1590,7 +1590,7 @@
buffer[sizeof(buffer)-1]='\x0';
write_to_logs_and_console(buffer,NSLOG_RUNTIME_WARNING,TRUE);

- /* decremement the number of running service checks */
+ /* decrement the number of running service checks */
if(currently_running_service_checks>0)
currently_running_service_checks--;

@@ -2380,7 +2380,7 @@
*temp_ptr=':';


- /* if we're not doing agressive host checking, let WARNING states indicate the host is up (fake the result to be STATE_OK) */
+ /* if we're not doing aggressive host checking, let WAR

...[email truncated]...


This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]