0 Members and 2 Guests are viewing this topic.
Quote from: akumaburn on November 24, 2013, 11:29:40 PMQuote from: nrpatten on November 24, 2013, 11:17:39 PMQuote from: tadspoles on November 24, 2013, 11:15:52 PMDon't let the door hit you where the good Lord split you.Really? if its no issue why dont you setup your own pool?. anyone that is running a pool that is cron based will face this issue.The client isn't timing out.. it's just delaying its response by ~<45 seconds... and only when a block is found.I'm guessing your wanting to access the coin daemon's other functions for keeping payout/transaction information up to date and this process is getting delayed and so your cronjobs are getting queued one after another.I suggest you put a command stopping a previous cronjob at the start of your script.This should help: http://superuser.com/questions/232144/how-to-stop-a-currently-running-cron-jobOr better yet, check if a cron is currently running and if so abort adding the new cronjob.I could help further if you gave me all the specifics.I understand that maybe timing out was the wrong word. i can split the crons up but i will still be faced with the same issue with block updates queueing up and it will just get bigger and bigger untill running block update will take days.
Quote from: nrpatten on November 24, 2013, 11:17:39 PMQuote from: tadspoles on November 24, 2013, 11:15:52 PMDon't let the door hit you where the good Lord split you.Really? if its no issue why dont you setup your own pool?. anyone that is running a pool that is cron based will face this issue.The client isn't timing out.. it's just delaying its response by ~<45 seconds... and only when a block is found.I'm guessing your wanting to access the coin daemon's other functions for keeping payout/transaction information up to date and this process is getting delayed and so your cronjobs are getting queued one after another.I suggest you put a command stopping a previous cronjob at the start of your script.This should help: http://superuser.com/questions/232144/how-to-stop-a-currently-running-cron-jobOr better yet, check if a cron is currently running and if so abort adding the new cronjob.I could help further if you gave me all the specifics.
Quote from: tadspoles on November 24, 2013, 11:15:52 PMDon't let the door hit you where the good Lord split you.Really? if its no issue why dont you setup your own pool?. anyone that is running a pool that is cron based will face this issue.
Don't let the door hit you where the good Lord split you.
Quote from: nrpatten on November 24, 2013, 11:37:10 PMQuote from: akumaburn on November 24, 2013, 11:29:40 PMQuote from: nrpatten on November 24, 2013, 11:17:39 PMQuote from: tadspoles on November 24, 2013, 11:15:52 PMDon't let the door hit you where the good Lord split you.Really? if its no issue why dont you setup your own pool?. anyone that is running a pool that is cron based will face this issue.The client isn't timing out.. it's just delaying its response by ~<45 seconds... and only when a block is found.I'm guessing your wanting to access the coin daemon's other functions for keeping payout/transaction information up to date and this process is getting delayed and so your cronjobs are getting queued one after another.I suggest you put a command stopping a previous cronjob at the start of your script.This should help: http://superuser.com/questions/232144/how-to-stop-a-currently-running-cron-jobOr better yet, check if a cron is currently running and if so abort adding the new cronjob.I could help further if you gave me all the specifics.I understand that maybe timing out was the wrong word. i can split the crons up but i will still be faced with the same issue with block updates queueing up and it will just get bigger and bigger untill running block update will take days.You forget that you wont always be in the "wait()" state, once every few minutes you'll get a cron to run right and you'll get all your block updates right then. It won't queue up as long as you make sure the jobs don't stack.
The developer has addressed you personally. He has told you his plans and where the situation is now. He has gone out of his way even offering personal assistance yet you still continue to publicly slander the coin. I am merely an investor. I simply don't like your approach and I believe you could have gone about it in a much more positive way.Hence, [beep ] off as far as I'm concerned.
Thanks for your quick work and dedication to keeping this going nrpatten!
That Frankincense seems to be working for ya tadspoles. I gota get me some