yep... each server runs successfully. I just looked at the 'TOP' of the webistrano server and found this - if it might help: top - 14:02:41 up 7 days, 9:59, 4 users, load average: 2.42, 2.17, 1.69 Tasks: 132 total, 3 running, 129 sleeping, 0 stopped, 0 zombie Cpu(s): 48.0%us, 2.4%sy, 0.0%ni, 49.6%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Mem: 2051948k total, 1152812k used, 899136k free, 227292k buffers Swap: 6004728k total, 0k used, 6004728k free, 351192k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 31392 www-data 20 0 139m 56m 3712 R 100 2.8 0:24.30 ruby script/runner -e production deployment = Deployment.find(273); deployment.prompt_config = 29375 www-data 20 0 137m 54m 3712 R 100 2.7 144:40.03 ruby script/runner -e production deployment = Deployment.find(254); deployment.prompt_config = 31205 www-data 20 0 144m 61m 2584 S 1 3.1 0:02.63 Rails: / var/rails/ webistrano 31399 root 20 0 19132 1340 980 R 0 0.1 0:00.10 top Seems like the Ruby is trashing the CPU for some reason.... On Nov 15, 8:46 pm, Lee Hambley <[email protected]> wrote: > Sure, but does that run, successfully - individually on both servers, > invidually? Might I ask the reason for a deploy to /usr/local > > -- Lee Hambley > > Twitter: @leehambley | @capistranorb -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to [email protected] * To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano?hl=en
