Content-Type: multipart/alternative; boundary=0016e6de03be63c197049c672ca9
--0016e6de03be63c197049c672ca9
Content-Type: text/plain; charset=ISO-8859-1
---------- Forwarded message ----------
From: Tevfik Karagulle
Date: Wed, Feb 16, 2011 at 2:25 PM
Subject: Re: [Nagios-devel] Fwd: Nagios core patches for External Command
support in Cygwin
To: Thomas Guyot-Sionnest
Hi Thomas,
There are more than 2000 downloads of Nagwin 1.0.1 containing the patch so
far and it seems that it works as expected: I haven't heard any issue
regarding the processing of external commands.
As you've suggested before, this patch can be implemented as a feature
rather than a part of Cygwin porting. Naming of the feature:
'use-plain-files-for-external-commands' ? Is it too long ?
'plain-files-for-external' ?
The CYGWIN file is then a very short one:
An experimental patch addressing problems with named pipes on Cygwin is
activated for building on Cygwin.
Attached you can find the README for the patch. Feedback is welcome! Patches
are available at
http://sourceforge.net/projects/sereds/ ... win/1.0.1/
Just let me know if you need more !!
Best regards
Tevfik
On Fri, Jan 28, 2011 at 4:58 AM, Thomas Guyot-Sionnest wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 11-01-27 10:31 PM, Tevfik Karagulle wrote:
> > Hi,
> >
> > Sounds good. I have already made some optimizations and it seems to work
> > as expected.
> >
> > Updated patch is now a part of the recently released Nagwin 1.0.1.
> > Source code is also available from Nagwin download address.
> >
> > I will wait one week or so to see how it performs. As you suggested, it
> > is better to implement it as a feature.
> >
> > Regarding documentation, what are your expectations
? Any examples> > or guidelines that can help ?
>
> For now, a "CYGWIN" file in the root dir where we can add instructions
> on building/using under cygwin will do. I'll make it cleat this is
> experimental...
>
> Your command pipe replacement should be documented in enough details for
> someone comfortable with Nagios to be able to use it (i.e. control
> Nagios with it) without reading the code.
>
> Thanks
>
> - --
> Thomas
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk1CPvsACgkQ6dZ+Kt5BchZlxQCgsIBxrlUB1xCBJe2jl+vTAEWa
> +zIAn0NsuRLLD8ymu/8PSPLLXXUA9DOX
> =DQfo
> -----END PGP SIGNATURE-----
>
--0016e6de03be63c197049c672ca9
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
---------- Forwarded message ----------From: Tevfik Karagulle <tevfik.karagulle@gmail=
.com>
Date: Wed, Feb 16, 2011 at 2:25 PMSubject: Re: [Nagios-devel] Fwd: Nagi=
os core patches for External Command support in CygwinTo: Thomas Guyot-=
Sionnest <[email protected]>
Hi Thomas,There are more than 2000 downloads of Nagwin 1.0.=
1 containing the patch so far and it seems that it works as expected: I hav=
en't heard any issue regarding the processing of external commands.
As you've suggested before, this patch can be implemented as a feat=
ure rather than a part of Cygwin porting. Naming of the feature:=A0 'us=
e-plain-files-for-external-commands' ? Is it too long ? 'plain-file=
s-for-external' ?
The CYGWIN file is then a very short one:An experimental patch addr=
essing problems with named pipes on Cygwin is activated for building on Cyg=
win.Attached you can find the README for the patch. Feedback is wel=
come! Patches are available at http://sourceforge.net/=
projects/sereds/files/Nagios/nagwin/1.0.1/
<b
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]