search for: despote

I am trying to use the new Rails 2.0 macro : rescue_from class PostsController < ApplicationController rescue_from ActiveRecord::RecordNotFound, :with => :deny_access ... def show @post = Post.find_by_id(params[:id]) raise ActiveRecord::RecordNotFound if @post.nil? #illegal access ..... end def deny_access respond_to do |format| format.html end end but the

Hello, I would like to find out the topology of an existing volume. For example, if I have a distributed replicated volume, what bricks are the replication partners? Fred -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20121114/b203ea91/attachment.html>

Hi, More related to the mailing list than to LARTC, can you explain why each time I send a mail to the mailing list lartc@mailman.ds9a.nl I get the following (BTW, my mail is correctly diffused..) : >>>>>>>>>>>>>>>>> -----Message d''origine----- De : Denis Sokolov [mailto:despot@ml.lv] Envoyé : lundi 18 octobre 2004 21:40 À : EC

I've searched all the archives and can't find anything relating to my problem. I have a 128 node cluster. Al NICS are Nvidia. I have them on a network with other machines. I do PXE installs of Fedora on them. These 128 nodes have a problem with the install. The initial DHCP requests get answered, the machine accepts and then the TFTP sequence takes place. The second DHCP request is

Reposted to this list: (http://lists.virus.org/voipsec-0610/msg00046.html) > That's exactly the type of thing that needs to be stopped. If Dell outsourcing calls me from India, the CLI must be their number in India not a faked-in number of some office in the US. That to me is exactly the purpose of this proposed law. It is equivalent to the law regarding FAX calls that has been

Greetings all, First off, thanks to everyone who contributed to the initial discussion thread. Judging by the responses from that thread, there seems to pretty broad interest in pursuing this. There also seem to be a few concerns. =] I'm including an updated draft based on the feedback, and I'll also try to break down the major points I've seen of discussion. Sorry for the long email,