Comments for Blog Without An Important Name http://www.kallisti.net.nz/blog I am not an IP address! I am a free 'blog! Fri, 08 Jan 2010 14:37:29 +1300 http://wordpress.org/?v=2.8.4 hourly 1 Comment on Kiwi Foo Camp 08 by Robin http://www.kallisti.net.nz/blog/2008/02/kiwi-foo-camp-08/comment-page-1/#comment-120393 Robin Fri, 08 Jan 2010 14:37:29 +0000 http://www.kallisti.net.nz/blog/2008/02/kiwi-foo-camp-08/#comment-120393 You will have to. I will be at the 2k10 one :) You will have to. I will be at the 2k10 one :)

]]> Comment on Kiwi Foo Camp 08 by thomas http://www.kallisti.net.nz/blog/2008/02/kiwi-foo-camp-08/comment-page-1/#comment-120392 thomas Fri, 08 Jan 2010 08:20:57 +0000 http://www.kallisti.net.nz/blog/2008/02/kiwi-foo-camp-08/#comment-120392 damn, i would've liked to attend that! i'm very interested in (and largely ignorant of) neural network theory and implementation. i should ask you a bit about it at foo 2010 :) damn, i would’ve liked to attend that! i’m very interested in (and largely ignorant of) neural network theory and implementation.

i should ask you a bit about it at foo 2010 :)

]]> Comment on Monitoring Puppet with Nagios by tikitu http://www.kallisti.net.nz/blog/2009/02/monitoring-puppet-with-nagios/comment-page-1/#comment-120391 tikitu Wed, 02 Dec 2009 15:03:38 +0000 http://www.kallisti.net.nz/blog/?p=82#comment-120391 And you were right! Moreover, the guy who *writes* that blog has exactly the same name as the guy who writes Robin's! Will the coincidences never stop?! And you were right! Moreover, the guy who *writes* that blog has exactly the same name as the guy who writes Robin’s! Will the coincidences never stop?!

]]> Comment on Monitoring Puppet with Nagios by Tom Eastman http://www.kallisti.net.nz/blog/2009/02/monitoring-puppet-with-nagios/comment-page-1/#comment-120390 Tom Eastman Thu, 26 Nov 2009 23:31:58 +0000 http://www.kallisti.net.nz/blog/?p=82#comment-120390 Through a random Google search trying to solve this exact problem, I went "oh, that guy's blog has the same name as Robin's" :-) Through a random Google search trying to solve this exact problem, I went “oh, that guy’s blog has the same name as Robin’s”

:-)

]]> Comment on Monitoring Puppet with Nagios by Dis http://www.kallisti.net.nz/blog/2009/02/monitoring-puppet-with-nagios/comment-page-1/#comment-120385 Dis Tue, 08 Sep 2009 13:53:01 +0000 http://www.kallisti.net.nz/blog/?p=82#comment-120385 We're using the state.yaml monitor, the problem is that it doesn't catch bad manifests. (The client will happily run off the cache in that case, and state.yaml gets a new timestamp.) We’re using the state.yaml monitor, the problem is that it doesn’t catch bad manifests. (The client will happily run off the cache in that case, and state.yaml gets a new timestamp.)

]]> Comment on Monitoring Puppet with Nagios by Robin http://www.kallisti.net.nz/blog/2009/02/monitoring-puppet-with-nagios/comment-page-1/#comment-120062 Robin Sun, 15 Mar 2009 07:04:57 +0000 http://www.kallisti.net.nz/blog/?p=82#comment-120062 That's not a bad idea, but my Perl script does that, and it also checks that the daemon is running immediately. A minor difference in practice I guess though, the script ageing thing will tell you eventually. That’s not a bad idea, but my Perl script does that, and it also checks that the daemon is running immediately. A minor difference in practice I guess though, the script ageing thing will tell you eventually.

]]> Comment on Monitoring Puppet with Nagios by Thomas Bergheim http://www.kallisti.net.nz/blog/2009/02/monitoring-puppet-with-nagios/comment-page-1/#comment-120061 Thomas Bergheim Sat, 14 Mar 2009 15:40:59 +0000 http://www.kallisti.net.nz/blog/?p=82#comment-120061 I am using a simple file check for this: /usr/lib/nagios/plugins/check_file_age -f /var/lib/puppet/state/state.yaml -w 5400 -c 7200 It will warn you if puppet isn't doing anything after 5400 seconds, and mark critical after 2 hours It picks up daemons locking up, compile errors, crashes, etc. The good thing ofcourse is that it doesn't have any dependancies! I am using a simple file check for this:

/usr/lib/nagios/plugins/check_file_age -f /var/lib/puppet/state/state.yaml -w 5400 -c 7200

It will warn you if puppet isn’t doing anything after 5400 seconds, and mark critical after 2 hours

It picks up daemons locking up, compile errors, crashes, etc.

The good thing ofcourse is that it doesn’t have any dependancies!

]]> Comment on Extension to the ‘Shunting Yard’ algorithm to allow variable numbers of arguments to functions by Steven Hughes http://www.kallisti.net.nz/blog/2008/02/extension-to-the-shunting-yard-algorithm-to-allow-variable-numbers-of-arguments-to-functions/comment-page-1/#comment-120051 Steven Hughes Wed, 04 Feb 2009 15:49:32 +0000 http://www.kallisti.net.nz/blog/2008/02/extension-to-the-shunting-yard-algorithm-to-allow-variable-numbers-of-arguments-to-functions/#comment-120051 Correction: 'Min(1,2) would be converted to '1 2 2 Min' Correction:

‘Min(1,2) would be converted to ‘1 2 2 Min’

]]> Comment on Extension to the ‘Shunting Yard’ algorithm to allow variable numbers of arguments to functions by Steven Hughes http://www.kallisti.net.nz/blog/2008/02/extension-to-the-shunting-yard-algorithm-to-allow-variable-numbers-of-arguments-to-functions/comment-page-1/#comment-120050 Steven Hughes Wed, 04 Feb 2009 15:47:00 +0000 http://www.kallisti.net.nz/blog/2008/02/extension-to-the-shunting-yard-algorithm-to-allow-variable-numbers-of-arguments-to-functions/#comment-120050 I recently wrote a calculator app for my Mobile 6 phone because the one that came with it did not support anything other than basic arithmetic. I performed the exact same 3 high-level steps that you used. In addition, I also found it helpful to modify the Shunting Yard algorithm. However, my modification was designed to validate that the correct number of parameters was passed to a function. I counted the number of commas in the parameter list using an arg count stack just like you did. One thing my modification did not do was to ensure that a value was in fact passed for each parameter. My modification was not able to detect null parameters (e.g. min(,3) - first parameter missing). It appears your 'were values' stack is designed for just such a purpose. I had a thought on how to handle a varialbe number of parameters and stil maintain a single postfix expression. If the Shunting Yard algorithm is modified to put the number of arguments passed to a function as the function's last parameter, you could easily handle variable numbers of parameters when you evaluate the postfix expression. 'Min(1,2,3,4,5)' would be converted to postfix as '1 2 3 4 5 5 Min'. The Min function would pop the last '5' (which would be on the top of the stack) and know it needed to pop 5 more values to get all it's parameters. Similarly, 'Min(1,2)' would be converted to '1 2 3 Min'. I have not, actually, implemented this but was thinking that it would probably be my approach if I were to. Of course, I would probably want to implement the null value check to so I didn't corrupt the stack by reading parameters meant for other operations. I recently wrote a calculator app for my Mobile 6 phone because the one that came with it did not support anything other than basic arithmetic. I performed the exact same 3 high-level steps that you used. In addition, I also found it helpful to modify the Shunting Yard algorithm. However, my modification was designed to validate that the correct number of parameters was passed to a function. I counted the number of commas in the parameter list using an arg count stack just like you did. One thing my modification did not do was to ensure that a value was in fact passed for each parameter. My modification was not able to detect null parameters (e.g. min(,3) – first parameter missing). It appears your ‘were values’ stack is designed for just such a purpose.

I had a thought on how to handle a varialbe number of parameters and stil maintain a single postfix expression. If the Shunting Yard algorithm is modified to put the number of arguments passed to a function as the function’s last parameter, you could easily handle variable numbers of parameters when you evaluate the postfix expression.

‘Min(1,2,3,4,5)’ would be converted to postfix as ‘1 2 3 4 5 5 Min’. The Min function would pop the last ‘5′ (which would be on the top of the stack) and know it needed to pop 5 more values to get all it’s parameters. Similarly, ‘Min(1,2)’ would be converted to ‘1 2 3 Min’.

I have not, actually, implemented this but was thinking that it would probably be my approach if I were to. Of course, I would probably want to implement the null value check to so I didn’t corrupt the stack by reading parameters meant for other operations.

]]> Comment on Setting the Content-Type on a subversion file by sanj http://www.kallisti.net.nz/blog/2006/08/setting-the-content-type-on-a-subversion-file/comment-page-1/#comment-120040 sanj Tue, 06 Jan 2009 04:50:31 +0000 http://www.kallisti.net.nz/blog/2006/08/setting-the-content-type-on-a-subversion-file/#comment-120040 Thanks mate! This had me confused for quite a while. Thanks mate! This had me confused for quite a while.

]]>