You can subscribe to this list here.
2007 |
Jan
|
Feb
(3) |
Mar
(8) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(6) |
Nov
(6) |
Dec
(6) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2008 |
Jan
(14) |
Feb
(3) |
Mar
(10) |
Apr
(73) |
May
(17) |
Jun
(2) |
Jul
(11) |
Aug
(21) |
Sep
(11) |
Oct
(9) |
Nov
(21) |
Dec
|
2009 |
Jan
|
Feb
(4) |
Mar
(2) |
Apr
(1) |
May
(7) |
Jun
(6) |
Jul
(1) |
Aug
(5) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
(1) |
2010 |
Jan
(2) |
Feb
(41) |
Mar
(71) |
Apr
(3) |
May
(7) |
Jun
(4) |
Jul
(6) |
Aug
(3) |
Sep
|
Oct
|
Nov
(16) |
Dec
(2) |
2011 |
Jan
(4) |
Feb
|
Mar
(8) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2012 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Eric S. <esc...@us...> - 2010-11-15 23:22:57
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Yes, I have done considerable testing with both DNX and Merlin. As of the most recent release of Merlin (0.9.0) distributed checks by hostgroup are working. DNX and Merlin work together nicely. At this time we're planning to deploy a campus wide infrastructure that leverages DNX and Merlin (Merlin for HA, DNX for load distribution). I never had a chance to test either of the patches for DNX, but I solved our hostgroup affinity problem with a few OpenVPN tunnels, so I only need HA and load-balancing now. <br> <br> Eric<br> <br> Sven Nierlein wrote: <blockquote cite="mid:4CE...@ni..." type="cite"> <pre wrap="">On 11/15/10 21:36, William Leibzon wrote: </pre> <blockquote type="cite"> <pre wrap="">DNX is maintained. </pre> </blockquote> <pre wrap=""><!----> Thats good to hear. However, i asked the question about putting hostgroup affinity into the core in march. But my questions got never answered. I am watching the DNX project over several years now, always looking forward for this feature. Btw, the hostgroup affinity patch is located here: <a class="moz-txt-link-freetext" href="https://github.com/Bakafish/DNX_Affinity/">https://github.com/Bakafish/DNX_Affinity/</a> I gave up waiting and wrote mod_gearman. mod_gearman tries a different approach. It uses already developed opensource software where possible and thus using the Gearman Jobserver for loadbalancing. There is hostgroup/servicegroup affinity already included in the core. And it is possible to distribute host checks and eventhandler too. If you want to have a look: <a class="moz-txt-link-freetext" href="https://github.com/sni/mod_gearman">https://github.com/sni/mod_gearman</a> And to be complete, you should also have a look at the merlin project, which also has hostgroup affinity included. Regards, Sven ------------------------------------------------------------------------------ Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! <a class="moz-txt-link-freetext" href="http://p.sf.net/sfu/dell-eql-dev2dev">http://p.sf.net/sfu/dell-eql-dev2dev</a> _______________________________________________ Dnx-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:Dnx...@li...">Dnx...@li...</a> <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/dnx-devel">https://lists.sourceforge.net/lists/listinfo/dnx-devel</a> </pre> </blockquote> </body> </html> |
From: Sven N. <sv...@ni...> - 2010-11-15 21:35:32
|
On 11/15/10 21:36, William Leibzon wrote: > DNX is maintained. Thats good to hear. However, i asked the question about putting hostgroup affinity into the core in march. But my questions got never answered. I am watching the DNX project over several years now, always looking forward for this feature. Btw, the hostgroup affinity patch is located here: https://github.com/Bakafish/DNX_Affinity/ I gave up waiting and wrote mod_gearman. mod_gearman tries a different approach. It uses already developed opensource software where possible and thus using the Gearman Jobserver for loadbalancing. There is hostgroup/servicegroup affinity already included in the core. And it is possible to distribute host checks and eventhandler too. If you want to have a look: https://github.com/sni/mod_gearman And to be complete, you should also have a look at the merlin project, which also has hostgroup affinity included. Regards, Sven |
From: William L. <wi...@le...> - 2010-11-15 21:10:42
|
http://sourceforge.net/mailarchive/forum.php?thread_name=40F86133-5397-4367-AB18-8363E465AB39%40forschooner.net&forum_name=dnx-devel There may have been a newer version but I can't quickly find it by just searching mail. On Mon, Nov 15, 2010 at 12:56 PM, Wright, Stephen <sw...@co...>wrote: > Everyone thanks for the replys. I think I will look at the patch that > would limit DNX to an IP range. I can apply the patch and test in our > environment. But if it’s not ready for prime time I will probably hold off > on deploying in our production environment. Thanks for the suggestions > about using mod_gearman. > > Stephen Wright Open Source Engineer | comScore, Inc. *(NASDAQ:SCOR)* > > o +1 (312) 777-8806 | sw...@co... > > > ........................................................................................................... > > *comScore* > > Measuring the Digital World > > > > *Introducing Video Metrix 2.0* > > The industry's first tool for understanding online video monetization > > www.videometrix2.com > > > > *From:* William Leibzon [mailto:wi...@le...] > *Sent:* Monday, November 15, 2010 2:36 PM > *To:* Rune 'TheFlyingcorpse' Darrud > *Cc:* dnx...@li... > *Subject:* Re: [Dnx-devel] Setting DNX Worker Service and Host Checks > > > > DNX is maintained. Don't spread rumors. > > There are two patches for DNX, one to do it based on hostgroup and one > based on network ip range (I think). None are included in the base because > there is not an agreement on how to do it or that code is ready as well as > some security issues how to decide who can do what. Plus big places that use > DNX and paid their developers to write it are not ready to test these > additions and that is really what is needed before this could be released as > part of dnx rather then on small-scale testing level that you are doing. I'm > personally in favor of hostgroup based method too. > > > > On Mon, Nov 15, 2010 at 10:40 AM, Rune 'TheFlyingcorpse' Darrud < > the...@gm...> wrote: > > Hello Stephen, > > However, mod_gearman allows this type of affinity right now(because > sadly DNX does not appear to be maintained?), based on per hostgroup! > I've helped to test it myself and currently use it in a small setup, > with a plan to go full production not too far into the future =) > > Regards, > Rune "TheFlyingCorpse" Darrud > > On 15 November 2010 19:09, Eric Schoeller > > <esc...@us...> wrote: > > Hi Stephen, > > > > What you're looking for is "DNX Worker Node Affinity", this is a highly > > requested feature. It's not currently available, but I know it's > somewhere > > on the DNX roadmap. If you look through the dnx-users (and perhaps > > dnx-devel) mail list archives you'll see a few discussions about it. > > > > Thanks for your interest in the DNX project, > > > > Eric > > > > Wright, Stephen wrote: > > > > Hello my name is Stephen Wright. DNX seems like a great module and a > > terrific replacement for NSCA. I did have one question though and I > wasn’t > > sure if this was the right forum. The company I work for uses Nagios in > a > > distributed environment. However we are monitoring items in several > > locations throughout the US. So for our California office we have a > Nagios > > server monitoring everything in our California office. For our New York > > server everything is monitoring at our New York location. All the > service > > results are then sent passively via NSCA to our central server in > Washington > > DC. I was wondering if there was a way DNX could limit which worker > node > > gets which checks. I.E. I would not want our New York worker node trying > to > > run a host or service check against a server in our California office or > > vice versa. Is there any way to specify which hosts, services, or host > > groups a worker can run checks against. If this is not the proper place > to > > ask questions could you please direct me to a place where I could ask > > questions. Thank you for any assistance. > > > > > > > > Stephen Wright Open Source Engineer | comScore, Inc. (NASDAQ:SCOR) > > > > o +1 (312) 777-8806 | sw...@co... > > > > > ........................................................................................................... > > > > comScore > > > > Measuring the Digital World > > > > > > > > Introducing Video Metrix 2.0 > > > > The industry's first tool for understanding online video monetization > > > > www.videometrix2.com > > > > > > > > ________________________________ > > > ------------------------------------------------------------------------------ > > Centralized Desktop Delivery: Dell and VMware Reference Architecture > > Simplifying enterprise desktop deployment and management using > > Dell EqualLogic storage and VMware View: A highly scalable, end-to-end > > client virtualization framework. Read more! > > http://p.sf.net/sfu/dell-eql-dev2dev > > > > ________________________________ > > _______________________________________________ > > Dnx-devel mailing list > > Dnx...@li... > > https://lists.sourceforge.net/lists/listinfo/dnx-devel > > > > > > > ------------------------------------------------------------------------------ > > Centralized Desktop Delivery: Dell and VMware Reference Architecture > > Simplifying enterprise desktop deployment and management using > > Dell EqualLogic storage and VMware View: A highly scalable, end-to-end > > client virtualization framework. Read more! > > http://p.sf.net/sfu/dell-eql-dev2dev > > _______________________________________________ > > Dnx-devel mailing list > > Dnx...@li... > > https://lists.sourceforge.net/lists/listinfo/dnx-devel > > > > > > > ------------------------------------------------------------------------------ > Centralized Desktop Delivery: Dell and VMware Reference Architecture > Simplifying enterprise desktop deployment and management using > Dell EqualLogic storage and VMware View: A highly scalable, end-to-end > client virtualization framework. Read more! > http://p.sf.net/sfu/dell-eql-dev2dev > _______________________________________________ > Dnx-devel mailing list > Dnx...@li... > https://lists.sourceforge.net/lists/listinfo/dnx-devel > > > > > > ------------------------------------------------------------------------------ > Centralized Desktop Delivery: Dell and VMware Reference Architecture > Simplifying enterprise desktop deployment and management using > Dell EqualLogic storage and VMware View: A highly scalable, end-to-end > client virtualization framework. Read more! > http://p.sf.net/sfu/dell-eql-dev2dev > _______________________________________________ > Dnx-devel mailing list > Dnx...@li... > https://lists.sourceforge.net/lists/listinfo/dnx-devel > > |
From: Wright, S. <sw...@co...> - 2010-11-15 20:57:12
|
------------------------------------------------------------------------------ Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev |
From: William L. <wi...@le...> - 2010-11-15 20:36:52
|
DNX is maintained. Don't spread rumors. There are two patches for DNX, one to do it based on hostgroup and one based on network ip range (I think). None are included in the base because there is not an agreement on how to do it or that code is ready as well as some security issues how to decide who can do what. Plus big places that use DNX and paid their developers to write it are not ready to test these additions and that is really what is needed before this could be released as part of dnx rather then on small-scale testing level that you are doing. I'm personally in favor of hostgroup based method too. On Mon, Nov 15, 2010 at 10:40 AM, Rune 'TheFlyingcorpse' Darrud < the...@gm...> wrote: > Hello Stephen, > > However, mod_gearman allows this type of affinity right now(because > sadly DNX does not appear to be maintained?), based on per hostgroup! > I've helped to test it myself and currently use it in a small setup, > with a plan to go full production not too far into the future =) > > Regards, > Rune "TheFlyingCorpse" Darrud > > On 15 November 2010 19:09, Eric Schoeller > <esc...@us...> wrote: > > Hi Stephen, > > > > What you're looking for is "DNX Worker Node Affinity", this is a highly > > requested feature. It's not currently available, but I know it's > somewhere > > on the DNX roadmap. If you look through the dnx-users (and perhaps > > dnx-devel) mail list archives you'll see a few discussions about it. > > > > Thanks for your interest in the DNX project, > > > > Eric > > > > Wright, Stephen wrote: > > > > Hello my name is Stephen Wright. DNX seems like a great module and a > > terrific replacement for NSCA. I did have one question though and I > wasn’t > > sure if this was the right forum. The company I work for uses Nagios in > a > > distributed environment. However we are monitoring items in several > > locations throughout the US. So for our California office we have a > Nagios > > server monitoring everything in our California office. For our New York > > server everything is monitoring at our New York location. All the > service > > results are then sent passively via NSCA to our central server in > Washington > > DC. I was wondering if there was a way DNX could limit which worker > node > > gets which checks. I.E. I would not want our New York worker node trying > to > > run a host or service check against a server in our California office or > > vice versa. Is there any way to specify which hosts, services, or host > > groups a worker can run checks against. If this is not the proper place > to > > ask questions could you please direct me to a place where I could ask > > questions. Thank you for any assistance. > > > > > > > > Stephen Wright Open Source Engineer | comScore, Inc. (NASDAQ:SCOR) > > > > o +1 (312) 777-8806 | sw...@co... > > > > > ........................................................................................................... > > > > comScore > > > > Measuring the Digital World > > > > > > > > Introducing Video Metrix 2.0 > > > > The industry's first tool for understanding online video monetization > > > > www.videometrix2.com > > > > > > > > ________________________________ > > > ------------------------------------------------------------------------------ > > Centralized Desktop Delivery: Dell and VMware Reference Architecture > > Simplifying enterprise desktop deployment and management using > > Dell EqualLogic storage and VMware View: A highly scalable, end-to-end > > client virtualization framework. Read more! > > http://p.sf.net/sfu/dell-eql-dev2dev > > > > ________________________________ > > _______________________________________________ > > Dnx-devel mailing list > > Dnx...@li... > > https://lists.sourceforge.net/lists/listinfo/dnx-devel > > > > > > > ------------------------------------------------------------------------------ > > Centralized Desktop Delivery: Dell and VMware Reference Architecture > > Simplifying enterprise desktop deployment and management using > > Dell EqualLogic storage and VMware View: A highly scalable, end-to-end > > client virtualization framework. Read more! > > http://p.sf.net/sfu/dell-eql-dev2dev > > _______________________________________________ > > Dnx-devel mailing list > > Dnx...@li... > > https://lists.sourceforge.net/lists/listinfo/dnx-devel > > > > > > > ------------------------------------------------------------------------------ > Centralized Desktop Delivery: Dell and VMware Reference Architecture > Simplifying enterprise desktop deployment and management using > Dell EqualLogic storage and VMware View: A highly scalable, end-to-end > client virtualization framework. Read more! > http://p.sf.net/sfu/dell-eql-dev2dev > _______________________________________________ > Dnx-devel mailing list > Dnx...@li... > https://lists.sourceforge.net/lists/listinfo/dnx-devel > |
From: Rune 'T. D. <the...@gm...> - 2010-11-15 18:41:04
|
Hello Stephen, However, mod_gearman allows this type of affinity right now(because sadly DNX does not appear to be maintained?), based on per hostgroup! I've helped to test it myself and currently use it in a small setup, with a plan to go full production not too far into the future =) Regards, Rune "TheFlyingCorpse" Darrud On 15 November 2010 19:09, Eric Schoeller <esc...@us...> wrote: > Hi Stephen, > > What you're looking for is "DNX Worker Node Affinity", this is a highly > requested feature. It's not currently available, but I know it's somewhere > on the DNX roadmap. If you look through the dnx-users (and perhaps > dnx-devel) mail list archives you'll see a few discussions about it. > > Thanks for your interest in the DNX project, > > Eric > > Wright, Stephen wrote: > > Hello my name is Stephen Wright. DNX seems like a great module and a > terrific replacement for NSCA. I did have one question though and I wasn’t > sure if this was the right forum. The company I work for uses Nagios in a > distributed environment. However we are monitoring items in several > locations throughout the US. So for our California office we have a Nagios > server monitoring everything in our California office. For our New York > server everything is monitoring at our New York location. All the service > results are then sent passively via NSCA to our central server in Washington > DC. I was wondering if there was a way DNX could limit which worker node > gets which checks. I.E. I would not want our New York worker node trying to > run a host or service check against a server in our California office or > vice versa. Is there any way to specify which hosts, services, or host > groups a worker can run checks against. If this is not the proper place to > ask questions could you please direct me to a place where I could ask > questions. Thank you for any assistance. > > > > Stephen Wright Open Source Engineer | comScore, Inc. (NASDAQ:SCOR) > > o +1 (312) 777-8806 | sw...@co... > > ........................................................................................................... > > comScore > > Measuring the Digital World > > > > Introducing Video Metrix 2.0 > > The industry's first tool for understanding online video monetization > > www.videometrix2.com > > > > ________________________________ > ------------------------------------------------------------------------------ > Centralized Desktop Delivery: Dell and VMware Reference Architecture > Simplifying enterprise desktop deployment and management using > Dell EqualLogic storage and VMware View: A highly scalable, end-to-end > client virtualization framework. Read more! > http://p.sf.net/sfu/dell-eql-dev2dev > > ________________________________ > _______________________________________________ > Dnx-devel mailing list > Dnx...@li... > https://lists.sourceforge.net/lists/listinfo/dnx-devel > > > ------------------------------------------------------------------------------ > Centralized Desktop Delivery: Dell and VMware Reference Architecture > Simplifying enterprise desktop deployment and management using > Dell EqualLogic storage and VMware View: A highly scalable, end-to-end > client virtualization framework. Read more! > http://p.sf.net/sfu/dell-eql-dev2dev > _______________________________________________ > Dnx-devel mailing list > Dnx...@li... > https://lists.sourceforge.net/lists/listinfo/dnx-devel > > |
From: Eric S. <esc...@us...> - 2010-11-15 18:10:06
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Hi Stephen,<br> <br> What you're looking for is "DNX Worker Node Affinity", this is a highly requested feature. It's not currently available, but I know it's somewhere on the DNX roadmap. If you look through the dnx-users (and perhaps dnx-devel) mail list archives you'll see a few discussions about it.<br> <br> Thanks for your interest in the DNX project,<br> <br> Eric <br> <br> Wright, Stephen wrote: <blockquote cite="mid:A3A27E7EB4DFE944A6387CADF470600033B76AE4@CSIADEBS02.office.comscore.com" type="cite"><!-- Template generated by Exclaimer Mail Disclaimers on 02:58:37 Monday, 1 November 2010 --> <style type="text/css">P.7b15d21a-79ca-41c5-82eb-00b59b976170 { MARGIN: 0cm 0cm 0pt } LI.7b15d21a-79ca-41c5-82eb-00b59b976170 { MARGIN: 0cm 0cm 0pt } DIV.7b15d21a-79ca-41c5-82eb-00b59b976170 { MARGIN: 0cm 0cm 0pt } TABLE.7b15d21a-79ca-41c5-82eb-00b59b976170Table { MARGIN: 0cm 0cm 0pt } DIV.Section1 { page: Section1 } </style><!-- Template generated by Exclaimer Mail Disclaimers on 02:58:37 Monday, 1 November 2010 --> <style type="text/css">P.0d516fb1-ffbf-49b1-a258-db53b0bafaba { MARGIN: 0cm 0cm 0pt } LI.0d516fb1-ffbf-49b1-a258-db53b0bafaba { MARGIN: 0cm 0cm 0pt } DIV.0d516fb1-ffbf-49b1-a258-db53b0bafaba { MARGIN: 0cm 0cm 0pt } TABLE.0d516fb1-ffbf-49b1-a258-db53b0bafabaTable { MARGIN: 0cm 0cm 0pt } DIV.Section1 { page: Section1 } </style> <meta http-equiv="Content-Type" content="text/html; "> <meta name="Generator" content="Microsoft Word 12 (filtered medium)"> <style> <!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:11.0pt; font-family:"Arial","sans-serif";} a:link, span.MsoHyperlink {mso-style-priority:99; color:#669900; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {mso-style-priority:99; color:#FF9900; text-decoration:underline;} span.EmailStyle17 {mso-style-type:personal-compose; font-family:"Arial","sans-serif"; color:windowtext;} .MsoChpDefault {mso-style-type:export-only;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in;} div.Section1 {page:Section1;} --> </style> <!--[if gte mso 9]><xml> <o:shapedefaults v:ext="edit" spidmax="1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext="edit"> <o:idmap v:ext="edit" data="1" /> </o:shapelayout></xml><![endif]--> <p class="7b15d21a-79ca-41c5-82eb-00b59b976170"></p> <p class="0d516fb1-ffbf-49b1-a258-db53b0bafaba"></p> <div class="Section1"> <p class="MsoNormal">Hello my name is Stephen Wright. DNX seems like a great module and a terrific replacement for NSCA. I did have one question though and I wasn’t sure if this was the right forum. The company I work for uses Nagios in a distributed environment. However we are monitoring items in several locations throughout the US. So for our California office we have a Nagios server monitoring everything in our California office. For our New York server everything is monitoring at our New York location. All the service results are then sent passively via NSCA to our central server in Washington DC. I was wondering if there was a way DNX could limit which worker node gets which checks. I.E. I would not want our New York worker node trying to run a host or service check against a server in our California office or vice versa. Is there any way to specify which hosts, services, or host groups a worker can run checks against. If this is not the proper place to ask questions could you please direct me to a place where I could ask questions. Thank you for any assistance. <o:p></o:p></p> </div> <p class="0d516fb1-ffbf-49b1-a258-db53b0bafaba"> </p> <p class="0d516fb1-ffbf-49b1-a258-db53b0bafaba"><span style="color: rgb(38, 68, 110); font-weight: bold;">Stephen</span> <span style="color: rgb(38, 68, 110); font-weight: bold;">Wright</span> <span style="color: rgb(38, 68, 110);">Open Source Engineer</span> | <font color="#26446e">comScore, Inc. <font size="1"><em>(NASDAQ:SCOR)</em></font></font></p> <p class="0d516fb1-ffbf-49b1-a258-db53b0bafaba"><span style="color: rgb(38, 68, 110);">o +1 (312) 777-8806 | </span><span style="color: rgb(38, 68, 110);"></span><span style="color: rgb(38, 68, 110);"><span style="color: rgb(38, 68, 110);"><a moz-do-not-send="true" href="mailto:sw...@co..." title="Click to send email to Wright, Stephen" target=""><span style="color: rgb(38, 68, 110);">sw...@co...</span></a></span></span></p> <p class="0d516fb1-ffbf-49b1-a258-db53b0bafaba"><font color="#1f497d">...........................................................................................................</font></p> <p class="7b15d21a-79ca-41c5-82eb-00b59b976170"><strong><font color="#26446e">comScore</font></strong></p> <p class="7b15d21a-79ca-41c5-82eb-00b59b976170"><font color="#26446e">Measuring the Digital World</font></p> <p class="7b15d21a-79ca-41c5-82eb-00b59b976170"> </p> <p class="7b15d21a-79ca-41c5-82eb-00b59b976170"><strong><font color="#cc6600">Introducing Video Metrix 2.0</font></strong></p> <p class="7b15d21a-79ca-41c5-82eb-00b59b976170">The industry's first tool for understanding online video monetization</p> <p class="7b15d21a-79ca-41c5-82eb-00b59b976170"><a moz-do-not-send="true" href="http://www.videometrix2.com">www.videometrix2.com</a></p> <p class="7b15d21a-79ca-41c5-82eb-00b59b976170"> </p> <pre wrap=""> <hr size="4" width="90%"> ------------------------------------------------------------------------------ Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! <a class="moz-txt-link-freetext" href="http://p.sf.net/sfu/dell-eql-dev2dev">http://p.sf.net/sfu/dell-eql-dev2dev</a></pre> <pre wrap=""> <hr size="4" width="90%"> _______________________________________________ Dnx-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:Dnx...@li...">Dnx...@li...</a> <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/dnx-devel">https://lists.sourceforge.net/lists/listinfo/dnx-devel</a> </pre> </blockquote> </body> </html> |
From: Wright, S. <sw...@co...> - 2010-11-01 19:16:02
|
Hello my name is Stephen Wright. DNX seems like a great module and a terrific replacement for NSCA. I did have one question though and I wasn’t sure if this was the right forum. The company I work for uses Nagios in a distributed environment. However we are monitoring items in several locations throughout the US. So for our California office we have a Nagios server monitoring everything in our California office. For our New York server everything is monitoring at our New York location. All the service results are then sent passively via NSCA to our central server in Washington DC. I was wondering if there was a way DNX could limit which worker node gets which checks. I.E. I would not want our New York worker node trying to run a host or service check against a server in our California office or vice versa. Is there any way to specify which hosts, services, or host groups a worker can run checks against. If this is not the proper place to ask questions could you please direct me to a place where I could ask questions. Thank you for any assistance. Stephen Wright Open Source Engineer | comScore, Inc. (NASDAQ:SCOR) o +1 (312) 777-8806 | sw...@co...<mailto:sw...@co...> ........................................................................................................... comScore Measuring the Digital World Introducing Video Metrix 2.0 The industry's first tool for understanding online video monetization www.videometrix2.com<http://www.videometrix2.com> |
From: Jason B. <ja...@fo...> - 2010-08-04 00:49:36
|
If I were to make a recommendation it would be to get the TCP transport working as it would simplify some of the affinity logic and help all users. I think the UDP transport was a good design decision for local hosts, but once you start sending packets over multiple hops the loss of a single packet is far more likely and it really gums things up as there is potentially no fallback from the nagios parent process when clients are remote. In the Affinity experimental branch ( http://github.com/Bakafish/DNX_Affinity ) I had to do a lot of work to deal with lost UDP packets, I think things could have been simplified if the transport was more robust. Jason > Hi, > > On 03/25/10 05:14, John Calcote wrote: >> Just thinking about this feature a little tonight. It won't be added >> till after the 0.20 release of DNX, which will happen soon. > > The 0.20 has been released in April. Are there any news on this topic? > Host affinity would > be very helpful in larger distributed setups. > > Thanks for the great work, > Sven > > ------------------------------------------------------------------------------ > The Palm PDK Hot Apps Program offers developers who use the > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > of $1 Million in cash or HP Products. Visit us here for more details: > http://p.sf.net/sfu/dev2dev-palm > _______________________________________________ > Dnx-devel mailing list > Dnx...@li... > https://lists.sourceforge.net/lists/listinfo/dnx-devel |
From: Sven N. <sv...@ni...> - 2010-08-03 15:16:35
|
Hi, On 03/25/10 05:14, John Calcote wrote: > Just thinking about this feature a little tonight. It won't be added > till after the 0.20 release of DNX, which will happen soon. The 0.20 has been released in April. Are there any news on this topic? Host affinity would be very helpful in larger distributed setups. Thanks for the great work, Sven |
From: Roger T. <rto...@fl...> - 2010-08-03 08:54:40
|
> Anyway, I think these cases of modifying results make sense, but since > the topic is being discussed I am interested in other opinions. Anyone > care to comment? > They make sense to me too. IMO, DNX *should* make an injection in the returned result always and only when there has been any anomaly in DNX. Being transparent doesn't mean being untraceable, it means not being intrusive. If DNX works as expected, let the plugins fail if they want. But if DNX has had any issue when executing a plugin (i.e. the stated above timeouts), it must notify the user, and an injection is the best way to me. Of course, I also vote for making the change. Cheers. Roger |
From: John C. <joh...@gm...> - 2010-07-31 18:57:33
|
Hi all, SVN revision 378 has the range check removed. In this revision (and later) DNX clients will report the true shell error code. Please note that in making this change, the [EC = x] text has been removed from the status message as well, but it's no longer necessary because it would be redundant with the code reported to Nagios anyway. The previous revision (377) contains the changes necessary to use the system WIFEXIT and WEXITSTATUS macros. John On 7/30/2010 4:06 PM, Adam Augustine wrote: > 1) Why would DNX do that? > A - See my other response. It was not the right thing to do. John's > change should fix that. > > 2) Why am I seeing checks that return -1 only when I use DNX? > A - This one is a little more complex and subtle. I don't think it is > DNX per-se that is doing it. > > You may see a different return code when running under DNX because the > DNX client may be running as a different user from Nagios, because the > DNX client is running from a different location in the network, > because DNX may run the check with different environment variables > (DNX does not currently pass the environment variables from the Nagios > server), and those reasons are just from the top of my head. > > Without knowing your setup, and because this seems to be intermittent, > something we have seen is a particular worker node for whatever reason > is configured slightly differently from the others (/etc/resolv.conf > didn't have a search domain, ntp.conf had a typo in one of the server > IPs, freetds.conf had an entry missing), so a particular plugin > behaves differently there than on all the other. > > On Fri, Jul 30, 2010 at 5:43 AM, Roger Torrentsgenerós > <rto...@fl...> wrote: >> I'm with Eric. The more transparent DNX is, the better we'll understand >> what happens when a check fails. >> >> However, the current situation is that DNX "translates" an out of scope >> exit to an exit 3, and passes it to Nagios together with the original >> status message with a prepended "[EC-1]" (which I assume it means exit >> code -1). The human parsing part is useful, but in my case having an >> UNKNOWN state also means triggering an alert, sending an SMS and maybe >> waking someone (probably me) up. >> >> Two questions come into my mind: >> >> - Why would DNX do that? >> >> We also have home-made checks. If one of my boys creates a check that >> returns out of scope codes, I'd like to see it as always have seen it. >> Adding translations is also adding complexity when tracing errors back, >> so I think it's much better DNX simply acts as a messenger and returns >> to Nagios the check result "as is". >> >> - Why am I seeing checks that return -1 only when I use DNX? >> >> I'm seeing one [EC-1] result every 4 or 5 minutes when I use DNX, >> including standard checks that come with the official nagios-plugins >> releases for RHEL5, for example check_ntp. The thing is if I disable >> DNX, I never get -1 status, or UNKNOWN "out of bounds", or whatever. I >> only get false positives when I use DNX. >> >> As John said, it has to be something related to the way DNX fetches exit >> status from the plugins and tries to understand them. I don't know if >> his recent commit will fix something (will try), but I'm pretty sure >> that if DNX simply forwarded whatever it got from the plugin to Nagios, >> instead of trying to "understand" it, we'd eliminate some complexity and >> DNX wouldn't be the one to blame, but the plugin itself. >> >> Cheers. >> >> Roger >> > ------------------------------------------------------------------------------ > The Palm PDK Hot Apps Program offers developers who use the > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > of $1 Million in cash or HP Products. Visit us here for more details: > http://p.sf.net/sfu/dev2dev-palm > _______________________________________________ > Dnx-devel mailing list > Dnx...@li... > https://lists.sourceforge.net/lists/listinfo/dnx-devel > |
From: Adam A. <aug...@gm...> - 2010-07-30 22:06:15
|
1) Why would DNX do that? A - See my other response. It was not the right thing to do. John's change should fix that. 2) Why am I seeing checks that return -1 only when I use DNX? A - This one is a little more complex and subtle. I don't think it is DNX per-se that is doing it. You may see a different return code when running under DNX because the DNX client may be running as a different user from Nagios, because the DNX client is running from a different location in the network, because DNX may run the check with different environment variables (DNX does not currently pass the environment variables from the Nagios server), and those reasons are just from the top of my head. Without knowing your setup, and because this seems to be intermittent, something we have seen is a particular worker node for whatever reason is configured slightly differently from the others (/etc/resolv.conf didn't have a search domain, ntp.conf had a typo in one of the server IPs, freetds.conf had an entry missing), so a particular plugin behaves differently there than on all the other. On Fri, Jul 30, 2010 at 5:43 AM, Roger Torrentsgenerós <rto...@fl...> wrote: > > I'm with Eric. The more transparent DNX is, the better we'll understand > what happens when a check fails. > > However, the current situation is that DNX "translates" an out of scope > exit to an exit 3, and passes it to Nagios together with the original > status message with a prepended "[EC-1]" (which I assume it means exit > code -1). The human parsing part is useful, but in my case having an > UNKNOWN state also means triggering an alert, sending an SMS and maybe > waking someone (probably me) up. > > Two questions come into my mind: > > - Why would DNX do that? > > We also have home-made checks. If one of my boys creates a check that > returns out of scope codes, I'd like to see it as always have seen it. > Adding translations is also adding complexity when tracing errors back, > so I think it's much better DNX simply acts as a messenger and returns > to Nagios the check result "as is". > > - Why am I seeing checks that return -1 only when I use DNX? > > I'm seeing one [EC-1] result every 4 or 5 minutes when I use DNX, > including standard checks that come with the official nagios-plugins > releases for RHEL5, for example check_ntp. The thing is if I disable > DNX, I never get -1 status, or UNKNOWN "out of bounds", or whatever. I > only get false positives when I use DNX. > > As John said, it has to be something related to the way DNX fetches exit > status from the plugins and tries to understand them. I don't know if > his recent commit will fix something (will try), but I'm pretty sure > that if DNX simply forwarded whatever it got from the plugin to Nagios, > instead of trying to "understand" it, we'd eliminate some complexity and > DNX wouldn't be the one to blame, but the plugin itself. > > Cheers. > > Roger > |
From: Adam A. <aug...@gm...> - 2010-07-30 20:29:45
|
I don't think making this change will hurt anything. Everyone is right, DNX should be as transparent as it reasonably can be, and this doesn't keep with that goal. As I recall, the original motivation for doing this was to highlight plugins that were having problems to distinguish them from DNX and Nagios problems. Nagios by default returns a CRITICAL for out-of-bounds return codes which (at the time) we also felt was wrong. Out-of-bounds seemed like it should be UNKNOWN instead. With the perspective of the intervening years it doesn't seem like much of an issue. Instead, it should have been something we petitioned Nagios to change. It is clearly not the proper role of DNX to interpret return codes. I vote for making the change. Parallel to this however, there are other cases where DNX does insert additional information into the status info field of the check results. "DNX: Plugin timeout" is one where we felt it was important to distinguish between a DNX executing plugin and a locallly (to Nagios) executing plugin. It also does this where DNX itself times out or has other problems John would be in a better position to enumerate all the cases where this occurs. Anyway, I think these cases of modifying results make sense, but since the topic is being discussed I am interested in other opinions. Anyone care to comment? Adam Augustine On Fri, Jul 30, 2010 at 10:47 AM, John Calcote <joh...@gm...> wrote: > Roger, > > On 7/30/2010 5:43 AM, Roger Torrentsgenerós wrote: >> I'm with Eric. The more transparent DNX is, the better we'll understand >> what happens when a check fails. > > I've got a query into Adam Augustine (copied on this message also) - > owner of the DNX project. I want his opinion before I commit any such > change that breaks backward compatibility. > >> However, the current situation is that DNX "translates" an out of scope >> exit to an exit 3, and passes it to Nagios together with the original >> status message with a prepended "[EC-1]" (which I assume it means exit >> code -1). The human parsing part is useful, but in my case having an >> UNKNOWN state also means triggering an alert, sending an SMS and maybe >> waking someone (probably me) up. >> >> Two questions come into my mind: >> >> - Why would DNX do that? > > I don't really know what the original motivation was. As I stated > earlier, it's been that way since the beginning, and I wasn't the > original maintainer. > >> We also have home-made checks. If one of my boys creates a check that >> returns out of scope codes, I'd like to see it as always have seen it. >> Adding translations is also adding complexity when tracing errors back, >> so I think it's much better DNX simply acts as a messenger and returns >> to Nagios the check result "as is". >> >> - Why am I seeing checks that return -1 only when I use DNX? > > This could have something to do with the way we were manually extracting > the shell exit code from the waitpid status value. I changed this code > to use the proper abstraction macros (WIFEXIT and WEXITSTATUS). I've > committed this code, but to check the results, you'd have to checkout > the latest source from subversion and build from scratch. It's not that > hard to do this, but you may wish to wait till we've decided what to do > with the [EC...] thing. Such a build may be more valuable to you at that > point. > > John > |
From: John C. <joh...@gm...> - 2010-07-30 16:47:18
|
Roger, On 7/30/2010 5:43 AM, Roger Torrentsgenerós wrote: > I'm with Eric. The more transparent DNX is, the better we'll understand > what happens when a check fails. I've got a query into Adam Augustine (copied on this message also) - owner of the DNX project. I want his opinion before I commit any such change that breaks backward compatibility. > However, the current situation is that DNX "translates" an out of scope > exit to an exit 3, and passes it to Nagios together with the original > status message with a prepended "[EC-1]" (which I assume it means exit > code -1). The human parsing part is useful, but in my case having an > UNKNOWN state also means triggering an alert, sending an SMS and maybe > waking someone (probably me) up. > > Two questions come into my mind: > > - Why would DNX do that? I don't really know what the original motivation was. As I stated earlier, it's been that way since the beginning, and I wasn't the original maintainer. > We also have home-made checks. If one of my boys creates a check that > returns out of scope codes, I'd like to see it as always have seen it. > Adding translations is also adding complexity when tracing errors back, > so I think it's much better DNX simply acts as a messenger and returns > to Nagios the check result "as is". > > - Why am I seeing checks that return -1 only when I use DNX? This could have something to do with the way we were manually extracting the shell exit code from the waitpid status value. I changed this code to use the proper abstraction macros (WIFEXIT and WEXITSTATUS). I've committed this code, but to check the results, you'd have to checkout the latest source from subversion and build from scratch. It's not that hard to do this, but you may wish to wait till we've decided what to do with the [EC...] thing. Such a build may be more valuable to you at that point. John |
From: Roger T. <rto...@fl...> - 2010-07-30 11:43:39
|
I'm with Eric. The more transparent DNX is, the better we'll understand what happens when a check fails. However, the current situation is that DNX "translates" an out of scope exit to an exit 3, and passes it to Nagios together with the original status message with a prepended "[EC-1]" (which I assume it means exit code -1). The human parsing part is useful, but in my case having an UNKNOWN state also means triggering an alert, sending an SMS and maybe waking someone (probably me) up. Two questions come into my mind: - Why would DNX do that? We also have home-made checks. If one of my boys creates a check that returns out of scope codes, I'd like to see it as always have seen it. Adding translations is also adding complexity when tracing errors back, so I think it's much better DNX simply acts as a messenger and returns to Nagios the check result "as is". - Why am I seeing checks that return -1 only when I use DNX? I'm seeing one [EC-1] result every 4 or 5 minutes when I use DNX, including standard checks that come with the official nagios-plugins releases for RHEL5, for example check_ntp. The thing is if I disable DNX, I never get -1 status, or UNKNOWN "out of bounds", or whatever. I only get false positives when I use DNX. As John said, it has to be something related to the way DNX fetches exit status from the plugins and tries to understand them. I don't know if his recent commit will fix something (will try), but I'm pretty sure that if DNX simply forwarded whatever it got from the plugin to Nagios, instead of trying to "understand" it, we'd eliminate some complexity and DNX wouldn't be the one to blame, but the plugin itself. Cheers. Roger On Thu, 2010-07-29 at 15:13 -0600, Eric Schoeller wrote: > John, > > Yep, that's exactly where I was heading with this. Now that I > understand what DNX is doing, I'm torn between the options. Having DNX > send the exact return code would be more consistent with how Nagios > works in general, as well as how other passive distributed monitoring > methods work. Do you know if there was a specific reason why DNX was > designed to behave this way? Would changing the code break anything > else? > > I'm also interested if anyone else has thoughts on the matter, I've > cc'd dnx-devel. At first glance I would vote for sending the original > return code all the way up to Nagios. But at the very least this > should be documented somewhere. > > Eric > > John Calcote wrote: > > Eric, > > > > Would you rather have dnx clients return the exact error code that > > was returned by the shell? > > > > If there are any other interested parties, please also respond here. > > This functionality has been this way in DNX forever. :) I don't mind > > changing it, but I want to make sure I won't break a bunch of people > > if I do. > > > > John > > > > On 7/29/2010 2:47 PM, Eric Schoeller wrote: > > > So you're basically saying that Roger's plugin is returning -1 and > > > DNX translates this to 3 when it passes it to Nagios? > > > > > > The default behavior for Nagios is to accept an out of bounds > > > return code, and report it as such with a "return code out of > > > bounds" message. I think you can configure what state nagios uses > > > for such instances. > > > > > > John Calcote wrote: > > > > Hi Roger, > > > > > > > > The following result codes are defined in the dnxPlugin.h header file: > > > > > > > > #define DNX_PLUGIN_RESULT_OK 0 // DNX plugin result: success. > > > > #define DNX_PLUGIN_RESULT_WARNING 1 //DNX plugin result: warning. > > > > #define DNX_PLUGIN_RESULT_CRITICAL 2 // DNX plugin result: critical. > > > > #define DNX_PLUGIN_RESULT_UNKNOWN 3 // DNX plugin result: unknown. > > > > > > > > There is code in the plugin handler that basically looks like this: > > > > > > > > int result = do-shell-command(...) > > > > if result < DNX_PLUGIN_RESULT_OK OR result > DNX_PLUGIN_RESULT_UNKNOWN then > > > > prepend "[EC <result>]" to resulting message text > > > > return DNX_PLUGIN_RESULT_UNKNOWN (3) > > > > > > > > Thus, no matter what the plugin's shell returns to DNX client, if it's > > > > outside the range of known results, the result returned to Nagios by DNX > > > > is 3 (result unknown), but the real shell result code is displayed in > > > > the text in the [EC <result>] value. Thus, whenever DNX returns a 3 > > > > (result unknown) to Nagios, it can provide the true result code for > > > > human parsing in the message text. > > > > > > > > Btw, I've committed a minor change that *may* reduce the number of such > > > > occurrences because on some systems the shell status code may be encoded > > > > in the waitpid status value a bit differently. We were assuming a > > > > particular format rather than using the macros designed to parse out the > > > > status code. > > > > > > > > Regards, > > > > John > > > > > > > > On 7/29/2010 10:48 AM, Roger Torrentsgenerós wrote: > > > > > > > > > Hi, > > > > > > > > > > I have noticed that sometimes, some checks status in Nagios are shown > > > > > like this: > > > > > > > > > > [EC -1]NTP OK: Offset 0.0007655997179 secs > > > > > > > > > > This is what dnxsrv.audit.log shows (debug=1): > > > > > > > > > > [Thu Jul 29 18:24:00.211 2010] DISPATCH: Job 125865: Worker > > > > > 195.10.10.170-aa80a8c0: /usr/libexec/nagios/plugins/chec > > > > > k_nrpe -H 192.168.128.222 -c "check_ntp" > > > > > [Thu Jul 29 18:24:00.211 2010] ASSIGN: Job 125865: Worker > > > > > 195.10.10.170-aa80a8c0: /usr/libexec/nagios/plugins/check_ > > > > > nrpe -H 192.168.128.222 -c "check_ntp" > > > > > [Thu Jul 29 18:24:00.312 2010] COLLECT: Job 125865: Worker > > > > > 195.10.10.170-aa80a8c0: /usr/libexec/nagios/plugins/check > > > > > _nrpe -H 192.168.128.222 -c "check_ntp" > > > > > > > > > > This is what dnxcld.debug.log says (debug=2): > > > > > > > > > > [Thu Jul 29 18:24:00.220 2010] dnxPluginExecute: > > > > > Executing /usr/libexec/nagios/plugins/check_nrpe -H 192.168.128.222 > > > > > -c "check_ntp" > > > > > > > > > > Nagios log says: > > > > > > > > > > [1280420649] SERVICE ALERT: streamer022.p4.bt.bcn;ntp;UNKNOWN;SOFT;1;[EC > > > > > -1]NTP OK: Offset 0.0007655997179 secs > > > > > > > > > > What is this "[EC-1]" thing? In all cases, the check result message says > > > > > OK, but returns an "exit 3" so Nagios treats it as an UNKNOWN state. And > > > > > every time, the next check of the same service (rescheduled or > > > > > automatic) always returns an OK, with exit status 0 and a correctly > > > > > formed status message. > > > > > > > > > > So can someone explain what is that thing, what does it mean and what's > > > > > for? > > > > > > > > > > Thanks a lot! > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > > > The Palm PDK Hot Apps Program offers developers who use the > > > > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > > > > of $1 Million in cash or HP Products. Visit us here for more details: > > > > http://p.sf.net/sfu/dev2dev-palm > > > > _______________________________________________ > > > > Dnx-users mailing list > > > > Dnx...@li... > > > > https://lists.sourceforge.net/lists/listinfo/dnx-users > > > > > > > > > > ------------------------------------------------------------------------------ > > > The Palm PDK Hot Apps Program offers developers who use the > > > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > > > of $1 Million in cash or HP Products. Visit us here for more details: > > > http://p.sf.net/sfu/dev2dev-palm > > > > > > _______________________________________________ > > > Dnx-users mailing list > > > Dnx...@li... > > > https://lists.sourceforge.net/lists/listinfo/dnx-users > > > > > > > > > ____________________________________________________________________ > > > > ------------------------------------------------------------------------------ > > The Palm PDK Hot Apps Program offers developers who use the > > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > > of $1 Million in cash or HP Products. Visit us here for more details: > > http://p.sf.net/sfu/dev2dev-palm > > > > ____________________________________________________________________ > > > > _______________________________________________ > > Dnx-users mailing list > > Dnx...@li... > > https://lists.sourceforge.net/lists/listinfo/dnx-users > > > ------------------------------------------------------------------------------ > The Palm PDK Hot Apps Program offers developers who use the > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > of $1 Million in cash or HP Products. Visit us here for more details: > http://p.sf.net/sfu/dev2dev-palm > _______________________________________________ Dnx-users mailing list Dnx...@li... https://lists.sourceforge.net/lists/listinfo/dnx-users |
From: Eric S. <esc...@us...> - 2010-07-29 21:13:18
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> John,<br> <br> Yep, that's exactly where I was heading with this. Now that I understand what DNX is doing, I'm torn between the options. Having DNX send the exact return code would be more consistent with how Nagios works in general, as well as how other passive distributed monitoring methods work. Do you know if there was a specific reason why DNX was designed to behave this way? Would changing the code break anything else?<br> <br> I'm also interested if anyone else has thoughts on the matter, I've cc'd dnx-devel. At first glance I would vote for sending the original return code all the way up to Nagios. But at the very least this should be documented somewhere. <br> <br> Eric<br> <br> John Calcote wrote: <blockquote cite="mid:4C5...@gm..." type="cite"> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> Eric,<br> <br> Would you rather have dnx clients return the exact error code that was returned by the shell? <br> <br> If there are any other interested parties, please also respond here. This functionality has been this way in DNX forever. :) I don't mind changing it, but I want to make sure I won't break a bunch of people if I do.<br> <br> John<br> <br> On 7/29/2010 2:47 PM, Eric Schoeller wrote: <blockquote cite="mid:4C5...@us..." type="cite"> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> So you're basically saying that Roger's plugin is returning -1 and DNX translates this to 3 when it passes it to Nagios?<br> <br> The default behavior for Nagios is to accept an out of bounds return code, and report it as such with a "return code out of bounds" message. I think you can configure what state nagios uses for such instances.<br> <br> John Calcote wrote: <blockquote cite="mid:4C5...@gm..." type="cite"> <pre wrap=""> Hi Roger, The following result codes are defined in the dnxPlugin.h header file: #define DNX_PLUGIN_RESULT_OK 0 // DNX plugin result: success. #define DNX_PLUGIN_RESULT_WARNING 1 //DNX plugin result: warning. #define DNX_PLUGIN_RESULT_CRITICAL 2 // DNX plugin result: critical. #define DNX_PLUGIN_RESULT_UNKNOWN 3 // DNX plugin result: unknown. There is code in the plugin handler that basically looks like this: int result = do-shell-command(...) if result < DNX_PLUGIN_RESULT_OK OR result > DNX_PLUGIN_RESULT_UNKNOWN then prepend "[EC <result>]" to resulting message text return DNX_PLUGIN_RESULT_UNKNOWN (3) Thus, no matter what the plugin's shell returns to DNX client, if it's outside the range of known results, the result returned to Nagios by DNX is 3 (result unknown), but the real shell result code is displayed in the text in the [EC <result>] value. Thus, whenever DNX returns a 3 (result unknown) to Nagios, it can provide the true result code for human parsing in the message text. Btw, I've committed a minor change that *may* reduce the number of such occurrences because on some systems the shell status code may be encoded in the waitpid status value a bit differently. We were assuming a particular format rather than using the macros designed to parse out the status code. Regards, John On 7/29/2010 10:48 AM, Roger Torrentsgenerós wrote: </pre> <blockquote type="cite"> <pre wrap="">Hi, I have noticed that sometimes, some checks status in Nagios are shown like this: [EC -1]NTP OK: Offset 0.0007655997179 secs This is what dnxsrv.audit.log shows (debug=1): [Thu Jul 29 18:24:00.211 2010] DISPATCH: Job 125865: Worker 195.10.10.170-aa80a8c0: /usr/libexec/nagios/plugins/chec k_nrpe -H 192.168.128.222 -c "check_ntp" [Thu Jul 29 18:24:00.211 2010] ASSIGN: Job 125865: Worker 195.10.10.170-aa80a8c0: /usr/libexec/nagios/plugins/check_ nrpe -H 192.168.128.222 -c "check_ntp" [Thu Jul 29 18:24:00.312 2010] COLLECT: Job 125865: Worker 195.10.10.170-aa80a8c0: /usr/libexec/nagios/plugins/check _nrpe -H 192.168.128.222 -c "check_ntp" This is what dnxcld.debug.log says (debug=2): [Thu Jul 29 18:24:00.220 2010] dnxPluginExecute: Executing /usr/libexec/nagios/plugins/check_nrpe -H 192.168.128.222 -c "check_ntp" Nagios log says: [1280420649] SERVICE ALERT: streamer022.p4.bt.bcn;ntp;UNKNOWN;SOFT;1;[EC -1]NTP OK: Offset 0.0007655997179 secs What is this "[EC-1]" thing? In all cases, the check result message says OK, but returns an "exit 3" so Nagios treats it as an UNKNOWN state. And every time, the next check of the same service (rescheduled or automatic) always returns an OK, with exit status 0 and a correctly formed status message. So can someone explain what is that thing, what does it mean and what's for? Thanks a lot! </pre> </blockquote> <pre wrap=""><!----> ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://p.sf.net/sfu/dev2dev-palm">http://p.sf.net/sfu/dev2dev-palm</a> _______________________________________________ Dnx-users mailing list <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Dnx...@li...">Dnx...@li...</a> <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/dnx-users">https://lists.sourceforge.net/lists/listinfo/dnx-users</a> </pre> </blockquote> <pre wrap=""><fieldset class="mimeAttachmentHeader"></fieldset> ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://p.sf.net/sfu/dev2dev-palm">http://p.sf.net/sfu/dev2dev-palm</a></pre> <pre wrap=""><fieldset class="mimeAttachmentHeader"></fieldset> _______________________________________________ Dnx-users mailing list <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Dnx...@li...">Dnx...@li...</a> <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/dnx-users">https://lists.sourceforge.net/lists/listinfo/dnx-users</a> </pre> </blockquote> <br> <pre wrap=""> <hr size="4" width="90%"> ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: <a class="moz-txt-link-freetext" href="http://p.sf.net/sfu/dev2dev-palm">http://p.sf.net/sfu/dev2dev-palm</a></pre> <pre wrap=""> <hr size="4" width="90%"> _______________________________________________ Dnx-users mailing list <a class="moz-txt-link-abbreviated" href="mailto:Dnx...@li...">Dnx...@li...</a> <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/dnx-users">https://lists.sourceforge.net/lists/listinfo/dnx-users</a> </pre> </blockquote> </body> </html> |
From: John C. <joh...@gm...> - 2010-06-18 19:04:48
|
Sorry Eric, I must have had something highlighted when I replied. Thunderbird thinks (and rightly so) that highlighted text in the original message is all that should be copied to the response and I didn't notice. Here's the original message: Bug: Get error "No rule to make target `../common/libcmn.la <http://libcmn.la>', needed by `dnxClient'." when attempting to compile and install dnx client. If you do a make all there are not errors. Install setup: RHEL 6 beta 64 bit Config options: ./configure CFLAGS="-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -g" Command run: make install-client Result: [root@chqpvul8335 dnx-0.20.1]# make install-client cd client && make install make[1]: Entering directory `/usr/local/src/dnx-0.20.1/client' Making install in . make[2]: Entering directory `/usr/local/src/dnx-0.20.1/client' gcc -DHAVE_CONFIG_H -I. -I.. -DSYSCONFDIR=\"/usr/local/nagios/etc\" -DSYSLOGDIR=\"/usr/local/nagios/var/log\" -DSYSRUNPATH=\"/usr/local/nagios/var/run/dnx\" -DLIBEXECDIR=\"/usr/local/nagios/libexec\" -DDNXUSER=\"nagios\" -DDNXGROUP=\"nagios\" -I../common -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -g -MT dnxClient-dnxClientMain.o -MD -MP -MF .deps/dnxClient-dnxClientMain.Tpo -c -o dnxClient-dnxClientMain.o `test -f 'dnxClientMain.c' || echo './'`dnxClientMain.c mv -f .deps/dnxClient-dnxClientMain.Tpo .deps/dnxClient-dnxClientMain.Po gcc -DHAVE_CONFIG_H -I. -I.. -DSYSCONFDIR=\"/usr/local/nagios/etc\" -DSYSLOGDIR=\"/usr/local/nagios/var/log\" -DSYSRUNPATH=\"/usr/local/nagios/var/run/dnx\" -DLIBEXECDIR=\"/usr/local/nagios/libexec\" -DDNXUSER=\"nagios\" -DDNXGROUP=\"nagios\" -I../common -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -g -MT dnxClient-dnxPlugin.o -MD -MP -MF .deps/dnxClient-dnxPlugin.Tpo -c -o dnxClient-dnxPlugin.o `test -f 'dnxPlugin.c' || echo './'`dnxPlugin.c mv -f .deps/dnxClient-dnxPlugin.Tpo .deps/dnxClient-dnxPlugin.Po gcc -DHAVE_CONFIG_H -I. -I.. -DSYSCONFDIR=\"/usr/local/nagios/etc\" -DSYSLOGDIR=\"/usr/local/nagios/var/log\" -DSYSRUNPATH=\"/usr/local/nagios/var/run/dnx\" -DLIBEXECDIR=\"/usr/local/nagios/libexec\" -DDNXUSER=\"nagios\" -DDNXGROUP=\"nagios\" -I../common -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -g -MT dnxClient-dnxWLM.o -MD -MP -MF .deps/dnxClient-dnxWLM.Tpo -c -o dnxClient-dnxWLM.o `test -f 'dnxWLM.c' || echo './'`dnxWLM.c mv -f .deps/dnxClient-dnxWLM.Tpo .deps/dnxClient-dnxWLM.Po gcc -DHAVE_CONFIG_H -I. -I.. -DSYSCONFDIR=\"/usr/local/nagios/etc\" -DSYSLOGDIR=\"/usr/local/nagios/var/log\" -DSYSRUNPATH=\"/usr/local/nagios/var/run/dnx\" -DLIBEXECDIR=\"/usr/local/nagios/libexec\" -DDNXUSER=\"nagios\" -DDNXGROUP=\"nagios\" -I../common -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -g -MT dnxClient-dnxClntProt.o -MD -MP -MF .deps/dnxClient-dnxClntProt.Tpo -c -o dnxClient-dnxClntProt.o `test -f 'dnxClntProt.c' || echo './'`dnxClntProt.c mv -f .deps/dnxClient-dnxClntProt.Tpo .deps/dnxClient-dnxClntProt.Po gcc -DHAVE_CONFIG_H -I. -I.. -DSYSCONFDIR=\"/usr/local/nagios/etc\" -DSYSLOGDIR=\"/usr/local/nagios/var/log\" -DSYSRUNPATH=\"/usr/local/nagios/var/run/dnx\" -DLIBEXECDIR=\"/usr/local/nagios/libexec\" -DDNXUSER=\"nagios\" -DDNXGROUP=\"nagios\" -I../common -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -g -MT dnxClient-pfopen.o -MD -MP -MF .deps/dnxClient-pfopen.Tpo -c -o dnxClient-pfopen.o `test -f 'pfopen.c' || echo './'`pfopen.c mv -f .deps/dnxClient-pfopen.Tpo .deps/dnxClient-pfopen.Po make[2]: *** No rule to make target `../common/libcmn.la <http://libcmn.la>', needed by `dnxClient'. Stop. make[2]: Leaving directory `/usr/local/src/dnx-0.20.1/client' make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/dnx-0.20.1/client' make: *** [install-client] Error 2 I'm not sure if this is the same bug (2347980) reported on SourceForge but I have added a comment with the same information. On 6/18/2010 10:37 AM, Eric Schoeller wrote: > What was the original build error? > > John Calcote wrote: >> Hi Kyle, >> >> Thanks for reporting this - unfortunately, I'm not sure how to fix it. >> libcmn.la is a common library consumed by both the client and the >> server. Thus it must be built first. If you enter the common directory >> and run make, and then enter the dnxClient directory and run make, it >> should work fine. >> >> If this library were only required by the client I could place its >> directory beneath dnxClient and then build it when make was run in the >> dnxClient directory, but it's also required by the server, so it must be >> built before either the client or the server can be built. >> >> Suggestions? >> >> John >> >> On 6/17/2010 11:22 AM, Kyle Martin wrote: >> >>> RHEL 6 beta 64 bit >>> >> >> >> ------------------------------------------------------------------------------ >> ThinkGeek and WIRED's GeekDad team up for the Ultimate >> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the >> lucky parental unit. See the prize list and enter to win: >> http://p.sf.net/sfu/thinkgeek-promo >> _______________________________________________ >> Dnx-devel mailing list >> Dnx...@li... >> https://lists.sourceforge.net/lists/listinfo/dnx-devel >> > > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > > > _______________________________________________ > Dnx-devel mailing list > Dnx...@li... > https://lists.sourceforge.net/lists/listinfo/dnx-devel > |
From: Eric S. <esc...@us...> - 2010-06-18 16:37:25
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> What was the original build error?<br> <br> John Calcote wrote: <blockquote cite="mid:4C1...@gm..." type="cite"> <pre wrap="">Hi Kyle, Thanks for reporting this - unfortunately, I'm not sure how to fix it. libcmn.la is a common library consumed by both the client and the server. Thus it must be built first. If you enter the common directory and run make, and then enter the dnxClient directory and run make, it should work fine. If this library were only required by the client I could place its directory beneath dnxClient and then build it when make was run in the dnxClient directory, but it's also required by the server, so it must be built before either the client or the server can be built. Suggestions? John On 6/17/2010 11:22 AM, Kyle Martin wrote: </pre> <blockquote type="cite"> <pre wrap="">RHEL 6 beta 64 bit </pre> </blockquote> <pre wrap=""><!----> ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: <a class="moz-txt-link-freetext" href="http://p.sf.net/sfu/thinkgeek-promo">http://p.sf.net/sfu/thinkgeek-promo</a> _______________________________________________ Dnx-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:Dnx...@li...">Dnx...@li...</a> <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/dnx-devel">https://lists.sourceforge.net/lists/listinfo/dnx-devel</a> </pre> </blockquote> </body> </html> |
From: John C. <joh...@gm...> - 2010-06-17 22:45:26
|
Hi Kyle, Thanks for reporting this - unfortunately, I'm not sure how to fix it. libcmn.la is a common library consumed by both the client and the server. Thus it must be built first. If you enter the common directory and run make, and then enter the dnxClient directory and run make, it should work fine. If this library were only required by the client I could place its directory beneath dnxClient and then build it when make was run in the dnxClient directory, but it's also required by the server, so it must be built before either the client or the server can be built. Suggestions? John On 6/17/2010 11:22 AM, Kyle Martin wrote: > > RHEL 6 beta 64 bit |
From: Kyle M. <mar...@gm...> - 2010-06-17 17:23:25
|
Bug: Get error "No rule to make target `../common/libcmn.la', needed by `dnxClient'." when attempting to compile and install dnx client. If you do a make all there are not errors. Install setup: RHEL 6 beta 64 bit Config options: ./configure CFLAGS="-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -g" Command run: make install-client Result: [root@chqpvul8335 dnx-0.20.1]# make install-client cd client && make install make[1]: Entering directory `/usr/local/src/dnx-0.20.1/client' Making install in . make[2]: Entering directory `/usr/local/src/dnx-0.20.1/client' gcc -DHAVE_CONFIG_H -I. -I.. -DSYSCONFDIR=\"/usr/local/nagios/etc\" -DSYSLOGDIR=\"/usr/local/nagios/var/log\" -DSYSRUNPATH=\"/usr/local/nagios/var/run/dnx\" -DLIBEXECDIR=\"/usr/local/nagios/libexec\" -DDNXUSER=\"nagios\" -DDNXGROUP=\"nagios\" -I../common -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -g -MT dnxClient-dnxClientMain.o -MD -MP -MF .deps/dnxClient-dnxClientMain.Tpo -c -o dnxClient-dnxClientMain.o `test -f 'dnxClientMain.c' || echo './'`dnxClientMain.c mv -f .deps/dnxClient-dnxClientMain.Tpo .deps/dnxClient-dnxClientMain.Po gcc -DHAVE_CONFIG_H -I. -I.. -DSYSCONFDIR=\"/usr/local/nagios/etc\" -DSYSLOGDIR=\"/usr/local/nagios/var/log\" -DSYSRUNPATH=\"/usr/local/nagios/var/run/dnx\" -DLIBEXECDIR=\"/usr/local/nagios/libexec\" -DDNXUSER=\"nagios\" -DDNXGROUP=\"nagios\" -I../common -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -g -MT dnxClient-dnxPlugin.o -MD -MP -MF .deps/dnxClient-dnxPlugin.Tpo -c -o dnxClient-dnxPlugin.o `test -f 'dnxPlugin.c' || echo './'`dnxPlugin.c mv -f .deps/dnxClient-dnxPlugin.Tpo .deps/dnxClient-dnxPlugin.Po gcc -DHAVE_CONFIG_H -I. -I.. -DSYSCONFDIR=\"/usr/local/nagios/etc\" -DSYSLOGDIR=\"/usr/local/nagios/var/log\" -DSYSRUNPATH=\"/usr/local/nagios/var/run/dnx\" -DLIBEXECDIR=\"/usr/local/nagios/libexec\" -DDNXUSER=\"nagios\" -DDNXGROUP=\"nagios\" -I../common -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -g -MT dnxClient-dnxWLM.o -MD -MP -MF .deps/dnxClient-dnxWLM.Tpo -c -o dnxClient-dnxWLM.o `test -f 'dnxWLM.c' || echo './'`dnxWLM.c mv -f .deps/dnxClient-dnxWLM.Tpo .deps/dnxClient-dnxWLM.Po gcc -DHAVE_CONFIG_H -I. -I.. -DSYSCONFDIR=\"/usr/local/nagios/etc\" -DSYSLOGDIR=\"/usr/local/nagios/var/log\" -DSYSRUNPATH=\"/usr/local/nagios/var/run/dnx\" -DLIBEXECDIR=\"/usr/local/nagios/libexec\" -DDNXUSER=\"nagios\" -DDNXGROUP=\"nagios\" -I../common -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -g -MT dnxClient-dnxClntProt.o -MD -MP -MF .deps/dnxClient-dnxClntProt.Tpo -c -o dnxClient-dnxClntProt.o `test -f 'dnxClntProt.c' || echo './'`dnxClntProt.c mv -f .deps/dnxClient-dnxClntProt.Tpo .deps/dnxClient-dnxClntProt.Po gcc -DHAVE_CONFIG_H -I. -I.. -DSYSCONFDIR=\"/usr/local/nagios/etc\" -DSYSLOGDIR=\"/usr/local/nagios/var/log\" -DSYSRUNPATH=\"/usr/local/nagios/var/run/dnx\" -DLIBEXECDIR=\"/usr/local/nagios/libexec\" -DDNXUSER=\"nagios\" -DDNXGROUP=\"nagios\" -I../common -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -g -MT dnxClient-pfopen.o -MD -MP -MF .deps/dnxClient-pfopen.Tpo -c -o dnxClient-pfopen.o `test -f 'pfopen.c' || echo './'`pfopen.c mv -f .deps/dnxClient-pfopen.Tpo .deps/dnxClient-pfopen.Po make[2]: *** No rule to make target `../common/libcmn.la', needed by `dnxClient'. Stop. make[2]: Leaving directory `/usr/local/src/dnx-0.20.1/client' make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/dnx-0.20.1/client' make: *** [install-client] Error 2 I'm not sure if this is the same bug (2347980) reported on SourceForge but I have added a comment with the same information. |
From: Hiren P. <hir...@gm...> - 2010-05-13 07:26:51
|
On Wed, 12 May 2010 16:35:59 -0400 Max <per...@we...> wrote: > > personally not as yet, but I'm confident that it will work, core hasn't changed enough to break neb module support. > > we like what dnx does, and were thinking of bringing those features into the core, instead of neb modules, as a default way of icinga doing checks. > > if we were to do this, we'd definitely prefer dnx developers joining in, instead of constantly watching for developments in dnx and then bringing those back info icinga. > > that was the reason I thought I'd see what the dnx developers think. > > thanks for the replies thus far. > > So you want the DNX team to stop doing this as a NEB module and make > it just be a part of Icinga core so that Nagios core and Nagios core > related projects then cannot use it? > > That sounds like a very politically motivated move and I would suggest > not doing it, having DNX usable by just Icinga will only make a number > of people mad at the Icinga team. > > I'd suggest maintaining NEB compatibility and just having Icinga > developers contribute to DNX instead. > okay fair enough. thanks for the responses. |
From: William L. <wi...@le...> - 2010-05-12 20:42:00
|
Don't auto-reject unless its a resource issue. If you login and check spam/unsubscribed folder once every couple months that is already better. On Wed, May 12, 2010 at 12:56 PM, Adam Augustine <aug...@gm...> wrote: > Just as a note, we periodically get emails sent to the list from > people who are not subscribed. These get put into a queue where they > sit until I take the time to sort through them, deleted the spam, and > pass through the legitimate ones. This obviously delays legitimate > emails. > > The frequency of legit emails from unsubscribed people is pretty low, > so I don't make a habit of checking the queues very often, which > further delays emails. > > I guess what I am saying is that if you want a quick response, you > probably want to subscribe to the list. > > Also, given the relative in-frequency of unsubscribed people posting > to the list, I am considering auto-rejecting those. That would give > the submitter some idea as to why their post didn't show up > immediately. It would also save me some tiny amount of time. > > Thoughts? > > ------------------------------------------------------------------------------ > > _______________________________________________ > Dnx-devel mailing list > Dnx...@li... > https://lists.sourceforge.net/lists/listinfo/dnx-devel > |
From: Max <per...@we...> - 2010-05-12 20:36:27
|
> personally not as yet, but I'm confident that it will work, core hasn't changed enough to break neb module support. > we like what dnx does, and were thinking of bringing those features into the core, instead of neb modules, as a default way of icinga doing checks. > if we were to do this, we'd definitely prefer dnx developers joining in, instead of constantly watching for developments in dnx and then bringing those back info icinga. > that was the reason I thought I'd see what the dnx developers think. > thanks for the replies thus far. So you want the DNX team to stop doing this as a NEB module and make it just be a part of Icinga core so that Nagios core and Nagios core related projects then cannot use it? That sounds like a very politically motivated move and I would suggest not doing it, having DNX usable by just Icinga will only make a number of people mad at the Icinga team. I'd suggest maintaining NEB compatibility and just having Icinga developers contribute to DNX instead. - max |
From: Adam A. <aug...@gm...> - 2010-05-12 19:56:25
|
Just as a note, we periodically get emails sent to the list from people who are not subscribed. These get put into a queue where they sit until I take the time to sort through them, deleted the spam, and pass through the legitimate ones. This obviously delays legitimate emails. The frequency of legit emails from unsubscribed people is pretty low, so I don't make a habit of checking the queues very often, which further delays emails. I guess what I am saying is that if you want a quick response, you probably want to subscribe to the list. Also, given the relative in-frequency of unsubscribed people posting to the list, I am considering auto-rejecting those. That would give the submitter some idea as to why their post didn't show up immediately. It would also save me some tiny amount of time. Thoughts? |