Nagios 1.1 TAC cgi formatting fix

[Ethan Galstad]

The commenting was a brain fart on my part.  CVS has been updated 
with this fix for a few days.


On 24 Jun 2003 at 11:15, Mikel Bauer wrote:

> As I noticed a few people are concerned about this, perhaps they should 
> fix it.
> 
> The problem is incomplete table structures.  The odd thing is, the 
> appropriate table code is in the source, but a </tr></table> is 
> commented out.
> 
> The offending comment is at line 1223 to 1226 of tac.c.  Simply remove 
> the open and close comments (/* */).
> 
> I'd make this a "patch", but I'm lazy, and this is an easy fix.
> 
> Recompile the tac.c file, and voila, no more formating errors.
> -- 
> Mikel Bauer
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: INetU
> Attention Web Developers & Consultants: Become An INetU Hosting Partner.
> Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
> INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
> _______________________________________________
> 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
> 



Ethan Galstad,
Nagios Developer
---
Email: nagios at nagios.org
Website: http://www.nagios.org



-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
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