similar to: Mongrel PID file permissions

Hi, Ssh -f forks itself in the background. Very usefull if you would like to e.g. tunnel munin over ssh. Now it's tricky to terminate one process if you have multiple running. It seems that ssh currently (looked at 5.1p1) has no write-pid-to-file functionality So I implemented a patch which do so. Tested it a little and it seems to work. Hopefully it is of any use in my form or inspires the

The full description of this bug is here: https://bugzilla.redhat.com/show_bug.cgi?id=838592 and the effect it has on OpenStack is described here: https://bugzilla.redhat.com/show_bug.cgi?id=835466#c9 Rich.

I: Program returns random data in a function E: libguestfs no-return-in-nonvoid-function guestmount.c:75 The function fuse_opt_add_opt_escaped has only one caller and a return code is not checked. Signed-off-by: Olaf Hering <olaf at aepfle.de> --- diff --git a/fuse/guestmount.c b/fuse/guestmount.c index 17e94ba..1eb0553 100644 --- a/fuse/guestmount.c +++ b/fuse/guestmount.c @@ -49,7 +49,7

I''m trying to make puppetlabs_spec_helper runs on Windows 7 to test my Puppet modules. Is this supported ? Because I encountered some problems: 1. symlinks were not created on Windows 7 (even if the functionnality are availabe). To manage that I added to rake_tasks.rb an ugly function: def make_link(source,target) ruby_platform =

I need a way to kill the ferret_server drb process programatically, so I can start/stop it as part of the capistrano deployment process. This should be as simple as adding some sort of stop method to ActsAsFerret::Remote::Server. I was just messing around and was able to do it by modifying method_missing to look for the :stop method and then calling DRb.thread.exit -- this is not good enough for

Hello, Thank you for your development of Mongrel, great job. :) I am using mongrel_cluster, but I have a problem where my rails application name includes a "." such as mydomain.com, which causes an error when generating the PID file for mongrel. I have attached below a diff of the current working copy in the trunk and the changes I made to overcome this problem. I kept your

Hi, I have an application which is dying horrible deaths (i.e. segmentation faults) in mid-flight, in production... And of course, I should fix it. But while I find and fix the bugs, I found something I think should be different - I can work on submitting a patch, as it is quite simple, but I might be losing something on my rationale. When Mongrel segfaults, it does not -obviously- get to clean

I''m trying to build wxruby-swig on windows with the idea of building a windows installer for it. I think that this would go a long way toward encouraging windows developers to try out wxruby-swig. What do you think? Are we far enough along to contemplate a release? Building wxruby-swig on windows is actually going pretty smoothly, but I want to build it with vc++ 7.1 to match the

Has anyone been able to get script/server to successfully use lighttpd on a Windows box? When I try to start the server I get: PROBLEM: Lighttpd is not available on your system (or not in your path) So then I add "C:\lighttpd\sbin" to the path for the console session, and it still fails with the same error. If anyone has some success with this I sure would like to know. Webrick

I am working on a gem that has needs to set dependencies conditionally when the gem is installed. I''ve done some digging around and it looks like i''m not alone in this need. http://stackoverflow.com/questions/4596606/rubygems-how-do-i-add-platform-specific-dependency # this is a long thread http://www.ruby-forum.com/topic/957999 The only way I can see to add dependencies to

Hi there, I''m using Mongrel (0.3.13 prerelease, installed today) to serve up some Rails apps in production. Everything works fine if I give all the appropriate options on the command line, such as: $ mongrel_rails start -c /home/mcornick/rails/mcornick.org/current -P log/mongrel.pid -l log/mongrel.log -e production -d -a 127.0.0.1 -p 6833 So, having accomplished that, I thought it

Support Requests item #12080, was opened at 2007-07-07 19:02 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=412&aid=12080&group_id=85 Category: Install Problem (example) Group: None Status: Open Resolution: None Priority: 3 Submitted By: Luke Bayes (lukebayes) Assigned to: Nobody (None) Summary: How would one add these packages as a dependency to a

I''ve heard of this before. Try running this line and send me the output ruby -e "p RUBY_PLATFORM" Nick Andreas Schwarz wrote: > I''m trying to build wxRuby 6.0 on Linux (Ubuntu). When I run make I get > an error because htmlproc.h is not found (it does not exist in the Linux > version of wxWidgets). I see that the html* object files are removed > from

Hi all, We''re attempting to use Ferret with the DRb server at the moment, and it doesn''t work, at all... = Executive Summary The DRb server process keeps on calling the remote index to the DRb server process... Which means DRb is calling itself, and itself, and itself, until Ruby kills the Thread with a SystemStackLevel error. = The excruciating details... # Mongrel is

I''m having no luck trying to daemonize mongrel running a camping server. When mongrel daemonizes, I get: /usr/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb:723:in `accept'': closed stream (IOError) from /usr/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/configurator.rb:293:in `join'' ... (This was after I disabled the unhandled exception catchall in the

Hi all, I''m trying to start Mongrel using a configuration file, but Mongrel complains: $ sudo mongrel_rails start --config /usr/local/www/xltester.com/config/mongrel.yml !!! Path to log file not valid: log/mongrel.log mongrel::start reported an error. Use mongrel_rails mongrel::start -h to get help. I''m using sudo above to replicate monit, not because I run Mongrel as root.

I''m looking at implementation of Mongrel::Stop.run: def run if @force @wait.to_i.times do |waiting| exit(0) if not File.exist? @pid_file sleep 1 end Mongrel::send_signal("KILL", @pid_file) if File.exist? @pid_file else Mongrel::send_signal("TERM", @pid_file) end end and a question arises:

Hey folks. Sorry for the SUPER long email but if you''ve been experiencing the same problems with restarting your mongrel cluster with Capistrano, then I have two solutions that have worked for me and I''m pretty sure will for you as well. THE PROBLEM I was having trouble restarting my clusters using Capistrano. I''ve seen this come up before on the mailing list and

Hello all... I know its been a while since the last one, but a new prerelease is available with a gratuitous increase in version numbers! gem install mongrel_cluster --source http://mongrel.rubyforge.org/releases/ This one has some new features in it that need to be tested on all unix platforms. Please run --clean and cluster::status on every *nix you can find. I run linux so the rest are up

Hi, I noticed one small possible error in the openssh-2.3.0p1/contrib/redhat/sshd.init script. In the stop option: stop) echo -n "Shutting down sshd: " if [ -f $PID_FILE ] ; then killproc sshd [ $RETVAL -eq 0 ] && rm -f /var/lock/subsys/sshd fi echo