Nagios Segmentation Fault

[Robert S. Galloway]

Hi Stan,

Thanks for the information about this being contributed code, but frankly
you should have left it at that. I do what I can to support open source
software. (I write documentation and how to docs.) But it sounds to me like
you believe that if I cannot contribute code that I shouldn't use it?? WTF?
Also, if you wanted to rant and flame someone, why don't you follow your own
advice and keep it off the list? 

Furthermore as the primary maintainers of the overall product, I think it is
very appropriate to ask Ethan or Karl to fix it, or at least test the
patches that have been contributed and include it in a release. Isn't that
what being a maintainer is all about?

Anyway, since you flamed me I felt it necessary to respond. I apologize to
the rest of the list participants for them getting both of the last two
e-mails in this thread, but I felt I needed to stand up for myself and the
rest of us that "don't do code".

If you'd like to respond to this, I invite you to e-mail me directly.

Have a better day Stan.

Sincerely,

Robert S. Galloway
Chief Network Security Engineer
IKANO Communications
...the Internet branding company
Official Data Networking Services Provider for the
Salt Lake Olympic Winter Games of 2002
Securityguy_AT_ikano.com
801-415-8089

-----Original Message-----
From: Stanley Hopcroft [mailto:Stanley.Hopcroft at IPAustralia.Gov.AU] 
Sent: Thursday, June 12, 2003 8:09 PM
To: Robert S. Galloway
Cc: nagios-users at lists.sourceforge.net
Subject: Re: [Nagios-users] Nagios Segmentation Fault

Dear Sir,

This has _nothing_ whatsoever to do with Messers Galstad or de Bisschop

On Thu, Jun 12, 2003 at 07:55:11PM -0600, Robert S. Galloway wrote:
> Just to put my two cents in on this. I was quite disappointed that this
> wasn't fixed with Nagios 1.1. It seems to me that this problem is going to
> get worse as more people upgrade to Mandrake 9 and RH8/9.
> 
> So how about it Ethan and Karl? Perhaps 1.1a with this issue patched?
> 

The embedded stuff is _all_ contributed code.

The incumbent embedded Perl maintainer, failed utterly to get his act
together with this stuff, and unfortunately for them, these men trusted
him to do it.

Send flames to me personally but do not bother the list with "it's 
borked, why isn't it fixed".

<rant>
If you want release management, regular updates and bug fixes, an 
account representative to 'negotiate with', then Open Source Software is 
not for you.

In fact it is precisely these requirements that people articulate when 
they choose commercial software because Real people loathe developers 
and software ("we don't do code, thanks"); they can't bear the thought 
of relying on someone they can't manipulate with a contract.  
All they want is the shrink wrapped plastic and the up front cost.

Read what people say who code: they have all the disappointments and 
pressures that you and I have - all the trappings of what passes for 
life in this world - yet they still manage to give back what they have 
received. 
</rant>

> Thanks,

Yours sincerely.

-- 
------------------------------------------------------------------------
Stanley Hopcroft
------------------------------------------------------------------------

'...No man is an island, entire of itself; every man is a piece of the
continent, a part of the main. If a clod be washed away by the sea,
Europe is the less, as well as if a promontory were, as well as if a
manor of thy friend's or of thine own were. Any man's death diminishes
me, because I am involved in mankind; and therefore never send to know
for whom the bell tolls; it tolls for thee...'

from Meditation 17, J Donne.



-------------------------------------------------------
This SF.NET email is sponsored by: eBay
Great deals on office technology -- on eBay now! Click here:
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
_______________________________________________
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