Content-Type: text/plain; charset=ISO-8859-1
---------- Forwarded message ----------
From: Tevfik Karagulle
Date: Thu, Jan 27, 2011 at 11:28 AM
Subject: Re: [Nagios-devel] Nagios core patches for External Command support
in Cygwin
To: Thomas Guyot-Sionnest
Hi,
No need to integrate that patch into the main stream at the moment. Maybe it
is too specific for a not-so-mainstream platform for Nagios world (cygwin).
I just wanted to get some feedback about the way I did. I can see that it
is not so straightforward to address needs of sysadmins sending their own
commands directly.
I will try to come up with some docs and optimizations. We can then discuss
if it is worthwhile to be a part of the standard distribution.
Tev
On Thu, Jan 27, 2011 at 4:34 AM, Thomas Guyot-Sionnest wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 11-01-26 07:05 PM, Tevfik Karagulle wrote:
> > Hi,
> >
> > As I tried to explain in a related post at Nagios-users
> > ,
> > Cygwin's named pipe support is somewhat broken and unstable at the
> moment.
> >
> > I've met that problem during the development of Nagwin. I've evaluated
> > several approaches and ended up with patching cmd.cgi and utils.c to
> > introduce an 'one-plain-file-for-each command' scheme. The basic reason
> > behind this decision is to use something working well at all
> > circumtances (file system/directories)
Not a> > perfect/sleek/state-of-art solution, but it should be more than enough
> > for an environment with average load. Patched nagios and cmd.cgi are
> > tested on several machines and seems to work without problems.
>
> Hi Tev,
>
> Thanks for your patch. I wouldn't have any objection committing the code
> itself as it's totally non-invasive for other platforms, OTOH it's
> missing any documentation on this alternative, especially how an
> external program could send commands to Nagios. Could you please write
> up something that would get the average sysadmin up to speed as to how
> this system works?
>
> Also, I would rather make this a configure option and turn it on by
> default on cygwin. What if next Cygwin release fixes named pipes?
>
> Thanks
>
> - --
> Thomas
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk1A578ACgkQ6dZ+Kt5BchY23ACgh9at+XoVPNiOXRyBH0FDH73W
> wKcAniKmuqL6k2Cl8G739dni2w397o7X
> =PrX6
> -----END PGP SIGNATURE-----
>
--0016e649da8a540520049ada4085
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
---------- Forwarded message ----------From: Tevfik Karagulle <tevfik.karagulle@gmail=
.com>
Date: Thu, Jan 27, 2011 at 11:28 AMSubject: Re: [Nagios-devel] Nagios c=
ore patches for External Command support in CygwinTo: Thomas Guyot-Sion=
nest <[email protected]>
Hi,No need to integrate that patch into the main stream at the =
moment. Maybe it is too specific for a not-so-mainstream platform for Nagio=
s world (cygwin).=A0I just wanted to get some feedback about the wa=
y I did. I can see that it is not so straightforward to address needs of sy=
sadmins sending their own commands directly.
I will try to come up with some docs and optimizations. We can then dis=
cuss if it is worthwhile to be a part of the standard distribution.=
Tev
On Thu, Jan 27, 2011 at 4:34 AM, Thomas Guyot-Sionnest &l=
t;[email protected]>=
; wrote:
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 2
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]