Bartenfield: Kellytk: why would you want to add cron to this?

Reist: Hylle: To initiate the JS script

Dela: Do you have a better suggestion?

Innamorato: Kellytk: with what I suggested, you don’t need a separate scheduler. You just write it yourself in Node. That check function is doing the exact same thing Cron would.

Pyscher: You could just leave it running making the petitions for you every minute

Norskog: Kellytk: so you just run your JS application once, and it runs forever, checking the file in the interval you’ve defined

Westre: I ***ume I’d use forever to ensure it’s running, as I do the other Node.js instances

Frair: Kellytk: you can use forever, yes

Boeh: Kellytk: is this related to the other Node.js applications you have though?

Scoma: Hylle: I think that’s a nice idea. Run it once, keep it running, and work off of a timer. That would allow me to dynamically tune the timer interval through the retrieved file, as well :-

Valladao: Depending on how related they are, you can even put this in those applications themselves.

Scalice: This is for lazy-propagation of node configuration

Bradford: Unless you’ve got some heavy processing to do, in which case a separate process would be nice

Bradica: Kellytk: why not use an existing tool for configuring nodes, like Puppet?

Renova: Hylle: That will come next. I like to develop rudimentary v1s

Eggenberg: I haven’t worked with it yet. I hear good things. What’s your experience been like working with Puppet Hylle?

Fletchen: Hey ya there, some time ago some of you folks here refereed me an URL about recursions and article is based on factorial example, Im sure most of you know what Im talking about, could someone remind me of this url please?

Eckle: Kellytk: I’m not an Ops person so I don’t really use it

Kalinoski: You know what Mate says about recursion

Kalinoski: Function surefire fn { surefirefn; }function fn surefire { fnsurefire; };

Mate: Kalinoski: InternalError: too much recursion

Kalinoski: That there’s never too much of it

Wisecarver: Hey could somebody please explain me, what’s wrong with my logic? http://jsfiddle.net/50qyuy26/1/ how does it result 24 ? because the way I solve it results 20 ?

Vititow: B function neverGonnagiveYouUp{ return neverGonnaletYouDow }; neverGonnaletYouDow = neverGonna

Eady: Hylle: error eval:13 };neverGonnaletYouDow = neverGonna; Referen . https://git.io/vZXei

Vanhekken: B function neverGonnagiveYouUp{ return neverGonnaletYouDow }; var letYouDown; neverGonna // strict mode is silly

Eady: Hylle: error eval:9 _x = letYouDow; ReferenceError: letYouDow is not defined . https://git.io/vZXeQ

Fothergill: B function neverGonnagiveYouUp{ return neverGonnaletYouDown }; var letYouDown; neverGonna // strict mode is silly

Eady: Hylle: error timeout, took over 4000ms

Kalinoski: RonRichie: your program is right

Zacarias: Kalinoski yeah I know the program is right lol I wanna know what’s wrong with how I think it’s doing it, so obviously it’s not solving in a way I think it does

Klickman: Kalinoski man. I know what recursion is, and I know how to calculate a factorial. that’s not my question

Kalinoski: You just said your logic was wrong

Kalinoski: And if you are arriving at 20 for 4! it must be

Defusco: Yeah I read it the question the same as you raypulver

Kalinoski: I honestly tried a few things in my head to figure out how you could arrive at 20

Stjean: Well lol then you both got it wrong. I know that my function works properly and I know !4 is 4 * 3 * 2 * 1, my question is, how does the *function* think about doing it? what’s the function’s pattern of solving it? because it doesn’t seem to do like 4 * 3 * 2 * 1. this is kinda hard to get across what I mean

Defusco: RonRichie: if two people read a question a certain way then *mayybeee* it wasn’t quite phrased fully