[hobbit] dialup directive not implemented?
Agreed; we use "dialup" on individual hosts that go off a lot (for example, on printers that departments insist on shutting down now and then to conserve power)....... I do not use the complex form, simple hosts only.
Kent C. Brodie - brodie at phys.mcw.edu Department of Physiology Medical College of Wisconsin (414) 456-8590 -----Original Message----- From: Rich Smrcina [mailto:rsmrcina at wi.rr.com] Sent: Tuesday, August 08, 2006 10:38 AM To: hobbit at hswn.dk Subject: Re: [hobbit] dialup directive not implemented?
We use dialup on individual hosts, not in the way that Mike describes. If you're coming up with a different way to identify hosts that should not go red nor notify when they are down, that's fine, as long as the capability is still there.
Henrik Stoerner wrote:
On Tue, Aug 08, 2006 at 09:03:04AM -0500, Mike Serra wrote:
I have a simple question about the "dialup" directive in bb-hosts, the one that is supposed to come immediately after a page or subpage directive, and is used to ping a range of hosts, like a modem pool. Our sysadmin tells me that he read (in a man page online?) that this directive is not implemented. And it's acting like it isn't: we can't get it to do anything, despite trying every possible syntax that could make sense. But on the other hand people online talk about this as if they're using it just fine. So -- is it implemented? We are using hobbit version 4.2-beta-20060605.
It was implemented some time ago, but I've had reports coming in over the past couple of months that it doesn't work in the 4.2 test releases that are out. I then asked if anyone was using it, because if not I'd prefer to just rip it out instead of trying to fix it - and so far noone has stepped forward to say they really need it.
So ... do you need it ? If people want it, I'd really rather implement it quite differently than the old BB implementation - as a normal network test associated with a host, e.g.
0.0.0.0 vpnpool.foo.com # iprange=172.16.1.1-172.16.1.100Regards, Henrik
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
-- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com
Catch the WAVV! http://www.wavv.org WAVV 2007 - Green Bay, WI - May 18-22, 2007
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
Same here. In some cases it's used to confiscate machines off developer teams that arent utilising them enough ;).
Craig
-----Original Message----- From: Brodie, Kent [mailto:brodie at mcw.edu] Sent: 08 August 2006 16:48 To: hobbit at hswn.dk Subject: RE: [hobbit] dialup directive not implemented?
Agreed; we use "dialup" on individual hosts that go off a lot (for example, on printers that departments insist on shutting down now and then to conserve power)....... I do not use the complex form, simple hosts only.
Kent C. Brodie - brodie at phys.mcw.edu Department of Physiology Medical College of Wisconsin (414) 456-8590 -----Original Message----- From: Rich Smrcina [mailto:rsmrcina at wi.rr.com] Sent: Tuesday, August 08, 2006 10:38 AM To: hobbit at hswn.dk Subject: Re: [hobbit] dialup directive not implemented?
We use dialup on individual hosts, not in the way that Mike describes. If you're coming up with a different way to identify hosts that should not go red nor notify when they are down, that's fine, as long as the capability is still there.
Henrik Stoerner wrote:
On Tue, Aug 08, 2006 at 09:03:04AM -0500, Mike Serra wrote:
I have a simple question about the "dialup" directive in bb-hosts, the one that is supposed to come immediately after a page or subpage directive, and is used to ping a range of hosts, like a modem pool. Our sysadmin tells me that he read (in a man page online?) that this directive is not implemented. And it's acting like it isn't: we can't get it to do anything, despite trying every possible syntax that could make sense. But on the other hand people online talk about this as if they're using it just fine. So -- is it implemented? We are using hobbit version 4.2-beta-20060605.
It was implemented some time ago, but I've had reports coming in over the past couple of months that it doesn't work in the 4.2 test releases that are out. I then asked if anyone was using it, because if not I'd prefer to just rip it out instead of trying to fix it - and so far noone has stepped forward to say they really need it.
So ... do you need it ? If people want it, I'd really rather implement it quite differently than the old BB implementation - as a normal network test associated with a host, e.g.
0.0.0.0 vpnpool.foo.com # iprange=172.16.1.1-172.16.1.100Regards, Henrik
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
-- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com
Catch the WAVV! http://www.wavv.org WAVV 2007 - Green Bay, WI - May 18-22, 2007
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
participants (2)
-
brodie＠mcw.edu
-
Craig_Whilding＠mentor.com