Content-Type: text/plain; charset=ISO-8859-1
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 orguidelines that can help ?
Tev
On Fri, Jan 28, 2011 at 4:15 AM, Thomas Guyot-Sionnest wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 11-01-27 04:01 PM, Tevfik Karagulle wrote:
> > 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.
>
> Thanks. Well, I believe there's no better place for this code - once you
> believe it's mature enough to be somewhat usable and properly
> documented. Cygwin isn't supported right now so we won't break anything,
> OTOH we'll give opportunity for others to look at it and add to it.
>
> - --
> Thomas
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk1CNLsACgkQ6dZ+Kt5BchbKIQCeK8yRUe+cB+I5L0La86VXxK13
> WGcAn07IlfyLT/S4aQIT2hRlb3YbYjd4
> =dc4G
> -----END PGP SIGNATURE-----
>
--0016e649da8af5e81a049adfb34c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
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 c=
ode 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 g=uidelines that can help ?
TevOn Fri, Jan 28, 2011 at 4:15 AM, Thom=
as Guyot-Sionnest <d=
[email protected]> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11-01-27 04:01 PM, Tevfik Karagulle wrote:
> 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).
>
> =A0I just wanted to get some feedback about the way I did. I can see t=
hat
> it is not so straightforward to address needs of sysadmins sending the=
ir
> 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.=
Thanks. Well, I believe there's no better place for this code - o=
nce you
believe it's mature enough to be somewhat usable and properly
documented. Cygwin isn't supported right now so we won't break anyt=
hing,
OTOH we'll give opportunity for others to look at it and add to it.
- --
Thomas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk1CNLsACgkQ6
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]