231 reputation
419
bio website facebook.com/thenonsequitur
location New York, NY
age 31
visits member for 3 years, 11 months
seen Nov 29 at 9:12
puts 10.downto(1).each{ |i| puts i }
puts 'Blast off!'

puts (10.downto(1).map{ |i| i.to_s } + ['Blast Off!']).join("\n")

(1..10).to_a.reverse.each{ |i| puts i }
puts 'Blast off!'

Apr
11
revised how to rewrite '%25' in url
added 2 characters in body
Apr
11
revised how to rewrite '%25' in url
added 479 characters in body
Apr
11
revised how to rewrite '%25' in url
added 479 characters in body
Apr
11
answered how to rewrite '%25' in url
Apr
3
accepted apt-get duplicate sources.list entry for google-chrome (Ubuntu 11.10)
Apr
3
comment apt-get duplicate sources.list entry for google-chrome (Ubuntu 11.10)
Yes, but after running apt-get a second time in a row, I wouldn't get errors the second time. Not that important, though. Problem solved is the important part!
Apr
3
comment apt-get duplicate sources.list entry for google-chrome (Ubuntu 11.10)
That fixed it thanks! Will mark this accepted when I can in 8 minutes :). Any idea why the warnings only showed up part of the time?
Apr
3
asked apt-get duplicate sources.list entry for google-chrome (Ubuntu 11.10)
Mar
28
accepted Any way to determine what “configure” parameters were used for current installation of nginx?
Mar
21
comment Not able to delete lot of files at once in linux
This isn't an directly related to your question, but after you succeed in deleting these old logs, look into logrotate to avoid this problem in the future: linuxcommand.org/man_pages/logrotate8.html
Mar
19
awarded  Self-Learner
Mar
19
answered Any way to determine what “configure” parameters were used for current installation of nginx?
Mar
19
asked Any way to determine what “configure” parameters were used for current installation of nginx?
Mar
15
awarded  Citizen Patrol
Mar
1
awarded  Yearling
Feb
27
answered Passenger + nginx: application doesn't run in production mode
Feb
25
comment Passenger + nginx: application doesn't run in production mode
@Fernando, none of my ideas were right :(. I'm out of ideas about what's going wrong, it really looks like some file just got corrupted somehow. If I were in your shoes at this point, I'd try re-installing all the agents by copying them from a standalone installation. Do you know how to do that? If not, I'll post it as an answer (because it may solve your problem).
Feb
23
comment Passenger + nginx: application doesn't run in production mode
Also, please post the output of this command on the server machine: ls -la /tmp | wc -l (this will tell you how many files are in the /tmp directory)
Feb
23
comment Passenger + nginx: application doesn't run in production mode
@Fernando, I have some ideas, but I need more info. Can you post your full nginx.conf? (just erase any sensitive information)
Feb
23
comment Passenger + nginx: application doesn't run in production mode
@Fernando, look at your nginx.conf for a line that looks like passenger_debug_log_file. That will tell you where the log file is.