This page is currently blank, and in the past had outdated info. I found this page, which is much more useful:
https://help.ubuntu.com/community/RubyOnRails
https://help.ubuntu.com/community/RubyOnRails
They're the things you would expect: mop the floors, sweep them, empty the trash, restock the cabinets.
And yet, when some psychologists interviewed hospital janitors to get a sense of what they thought their jobs were like, they encountered Mike, who told them about how he stopped mopping the floor because Mr. Jones was out of his bed getting a little exercise, trying to build up his strength, walking slowly up and down the hall. And Charlene told them about how she ignored her supervisor's admonition and didn't vacuum the visitor's lounge because there were some family members who were there all day, every day who, at this moment, happened to be taking a nap. And then there was Luke, who washed the floor in a comatose young man's room twice because the man's father, who had been keeping a vigil for six months, didn't see Luke do it the first time, and his father was angry. And behavior like this from janitors, from technicians, from nurses and, if we're lucky now and then, from doctors, doesn't just make people feel a little better, it actually improves the quality of patient care and enables hospitals to run well.
~/railsapp]$ ./script/console production
~/railsapp]$ ./script/console --sandbox
stats_start_collector: This is always on so it is not necessary to configure in PostgreSQL 8.3
stats_command_string: This is now called track_activities.
stats_block_level: This is now combined with stats_row_level and renamed to track_counts
stats_row_level: This is now combined with stats_block_level and renamed to track_counts
stats_reset_on_server_start: This is no longer necessary and is not a configuration option anymore
So now the only additions you will need to make to collect all of the stats you need will be track_counts and track_activities.
Example Configuration Addition:
track_activities = on
track_counts = on
To test that you are collecting the stats run the following command:
select * from pg_stat_all_tables;
# catch most exceptions (anything that derives from StandardError)
begin
...
rescue
puts $!, $@
end
# catch all exceptions (anything that derives from Exception)
begin
...
rescue Exception
puts $!, $@
end
end
begin
...
rescue Exception => ex
puts ex.message
puts ex.backtrace.join("\n")
end
$ git push origin :somebranch
error: unable to push to unqualified destination: somebranch
The destination refspec neither matches an existing ref on the remote nor
begins with refs/, and we are unable to guess a prefix based on the source ref.
fatal: The remote end hung up unexpectedly
error: failed to push some refs to 'git@my_server:my_repo.git'
$ git remote prune origin
Pipe viewer is a terminal-based tool for monitoring the progress of data through a pipeline. It can be inserted into any normal pipeline between two processes to give a visual indication of how quickly data is passing through, how long it has taken, how near to completion it is, and an estimate of how long it will be until completion.
$ pv access.log | gzip > access.log.gz
611MB 0:00:11 [58.3MB/s] [=> ] 15% ETA 0:00:59
sudo apt-get install ubuntu-desktop
sudo apt-get install xubuntu-desktop
sudo apt-get install kubuntu-desktop
sudo apt-get remove xubuntu-desktop
sudo apt-get autoremove
class Square < ActiveRecord::Base
def side=(value)
area = value * value
side = value
end
end
class Square < ActiveRecord::Base
def side=(value)
self.attributes['side'] = value
self.area = value * value
end
end
class Square < ActiveRecord::Base
def side=(value)
self.area = value * value
# This would still work because we're calling the default setter for area
write_attribute('side', value)
end
end