similar to: Running mongrel globally

Patches item #6335, was opened at 2006-10-26 16:51 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=413&aid=6335&group_id=85 Category: win32-shortcut Group: None Status: Open Resolution: None Priority: 3 Submitted By: Jano Svitok (janek) Assigned to: Nobody (None) Summary: pure ruby implementation Initial Comment: This is (not finished) pure-ruby

Bugs item #4598, was opened at 2006-05-29 11:20 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=411&aid=4598&group_id=85 Category: win32-eventlog Group: None Status: Open Resolution: None Priority: 3 Submitted By: Nobody (None) Assigned to: Nobody (None) Summary: possible wrong condition Initial Comment: Is this condition right? (eventlog.rb, line 494

Hi, why are the gemplugins commented out in mongrel_service? What was the problem with them? I''m curiuos because I''ve used them without problems since the revision 338 (-win32 suffix patch, 31/08). However, my site is a small internal one, so it doesn''t mean any heavy testing. Jano

I posted this to the discussion forum on rubyforge.org, but it appears that it would have been better to post here. Does anyone have any advice on how to resolve the problem reported at http://rubyforge.org/tracker/index.php?func=detail&aid=6284&group_id=1306&atid=5145? Thanks, Justin -------------- next part -------------- An HTML attachment was scrubbed... URL:

I''m trying to run mongrel on port 80 and switch to a different user/group from root. As root, this works: mongrel_rails start -p 3000 -u rails --group rails This: mongrel_rails start -p 80 -u rails --group rails dies with: --------------------------- ** Changing group to rails. ** Changing user to rails. ** Starting Mongrel listening at 0.0.0.0:80

Alright, this time a small announce going out to *just* the mongrel list so I can get some early testing. There''s a new pre-release of 0.3.13.4 out that includes the win32 version of the gem. ** WIN32 USERS SHOULD INSTALL THIS AND TEST.*** ***** BUT NOT ON PRODUCTION SYSTEMS. ****** As usual, you install it with: sudo gem install mongrel --source=http://mongrel.rubyforge.org/releases/

Patches item #6236, was opened at 2006-10-19 07:10 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=413&aid=6236&group_id=85 >Category: windows-pr Group: None Status: Open Resolution: None Priority: 3 Submitted By: Jano Svitok (janek) >Assigned to: Daniel Berger (djberg96) Summary: Add debug API Initial Comment: This adds couple of methods to

Patches item #6237, was opened at 2006-10-19 07:11 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=413&aid=6237&group_id=85 >Category: windows-pr Group: None Status: Open Resolution: None Priority: 3 Submitted By: Jano Svitok (janek) >Assigned to: Daniel Berger (djberg96) Summary: Add Guid API Initial Comment: This adds API for creating GUIDs.

Patches item #6237, was opened at 2006-10-19 16:11 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=413&aid=6237&group_id=85 Category: None Group: None Status: Open Resolution: None Priority: 3 Submitted By: Jano Svitok (janek) Assigned to: Nobody (None) Summary: Add Guid API Initial Comment: This adds API for creating GUIDs.

Patches item #6236, was opened at 2006-10-19 16:10 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=413&aid=6236&group_id=85 Category: None Group: None Status: Open Resolution: None Priority: 3 Submitted By: Jano Svitok (janek) Assigned to: Nobody (None) Summary: Add debug API Initial Comment: This adds couple of methods to interface with debugger (WinDbg,

I tried to install Rails + Mongrel on CentOS4.3 64Bit (my provider only has the 64 Bit version available). I found out, that I have to install gcc and emacs-common and have to copy the *.h files of the ruby source into a certain directory (see below). But finally I get an error messag when I start mongrel and I have no idea how to solve that problem: wget

Apologizes in advance if this sounds rather dense, but I want to make sure I''m understanding everything correctly. We''re in the process of migrating from Apache2.0/FastCGI to Apache2.0+mongrel (why not 2.2? that story is too long and too uninteresting to recount here, but I will tell you that it involves RHEL and only using RHN rpms). The init script that comes with mongrel

Hi, I wanted to set port in config file (via mongrel_rails -C config/config.yaml), and it seems to not take it into account. I''ve looked into the code, (line 58), and it reads: settings = conf.merge(settings) Now settings contain all the possible (important) keys (possibly with nil values, line 49, and lib/mongrel/command.rb, line 46) so everything from conf get overwritten with

In the latest windows binary (2007-04-03 r41023) pdf() with an argument paper="a4" gives an error, this was still ok in (2007-03-18 r40854) Jan Oosting > pdf("test.pdf",paper="a4") Error in pdf("test.pdf", paper = "a4") : invalid paper type 'a4' (pdf) > sessionInfo() R version 2.5.0 alpha (2007-04-03 r41023) i386-pc-mingw32

This patch: - adds --prefix option to service::install in mongrel-service plugin - fixes bug with config values merging in the service - enables gemplugins in the service. Questions: - why the load_plugins command was commented out? It seems working for me. - why bin/mongrel_rails_service and bin/mongrel_rails_svc still in the main package? - a lot of code is duplicated in both versions

Hi folks, For the past weeks I have been working in solve the problems with mongrel_service and its *crazy* behavior related to standard mongrel_rails. Job made this more slow than usual, but here we are: a beta release. * What''s New? - This version of mongrel_service replaces mongrel_service ruby script with a binary, pre-built executable coded using ServiceFB framework [1] in

https://bugs.freedesktop.org/show_bug.cgi?id=71662 Priority: medium Bug ID: 71662 Assignee: nouveau at lists.freedesktop.org Summary: [nvd9 regression] 3d application hang Severity: normal Classification: Unclassified OS: All Reporter: jano.vesely at gmail.com Hardware: Other Status: NEW

Hello, According to the docs, vcpupin will use either cgroups or sched_setaffinity to pin vcpu threads to cpus. How is this decision made? I observe differences even on different hosts featuring the same version of libvirtd (1.3.1): on one host vcpupin affects cpuset.cpus (cgroup), and on the other it affects vcpu threads affinity (observed through taskset). Thanks, Nikos -------------- next

https://bugs.freedesktop.org/show_bug.cgi?id=55948 Priority: medium Bug ID: 55948 Assignee: nouveau at lists.freedesktop.org Summary: [nvd9 optimus] drm/nouveau/bios: attempt to fetch entire acpi rom image in one shot breaks module load QA Contact: xorg-team at lists.x.org Severity: major Classification:

Greetings, when execute lspci inside my vm linux guest, I see this: :/# lspci | grep -i scsi 03:00.0 SCSI storage controller: Red Hat, Inc Virtio block device (rev 01) I don't see any such address in my xml file, is it possible to move that controller to another pci addr? Thanks, Dagg.