# Linux ps reports mongrel as \[ruby18\]

**URL:** <https://www.ruby-forum.com/t/linux-ps-reports-mongrel-as-ruby18/160609>\
**Category:** Mongrel\
**Created:** [February 18, 2009, 5:32am UTC](https://www.ruby-forum.com/t/linux-ps-reports-mongrel-as-ruby18/160609 "2009-02-18T05:32:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![devtheo](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/9de0a6/32.png) [@devtheo](https://www.ruby-forum.com/u/devtheo)\
**Post date:** [February 18, 2009, 5:32am UTC](https://www.ruby-forum.com/t/linux-ps-reports-mongrel-as-ruby18/160609/1 "2009-02-18T05:32:35Z")

</div>

I’m running two sets of mongrels using mongrel 1.1.4, one for production  
one for staging. When executing ‘ps’ from a linux shell, the production  
mongrels report as expected, however the staging processes are listed as  
[ruby 18]. The result seems to be that mongrel\_rails cannot stop the  
staging processes because it doesn’t recognize [ruby18] as a mongrel  
process.

I’ve read that this was a problem in older versions of mongrel and  
fixable by editing the init.rb file. The same posts seem to indicate  
that it is a problem with the kernel on my linux box. I can’t change  
the kernel on this box, so how can I get mongrel\_rails to stop the  
[ruby18] processes?

The same scripts/version of mongrel were running fine on a different  
box. The sites were just upgraded to new boxes, apparently with new  
kernels. Thanks for any help.

---

<div class="post-metadata">

**Author:** ![devtheo](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/9de0a6/32.png) [@devtheo](https://www.ruby-forum.com/u/devtheo)\
**Post date:** [February 20, 2009, 2:41pm UTC](https://www.ruby-forum.com/t/linux-ps-reports-mongrel-as-ruby18/160609/2 "2009-02-20T14:41:36Z")

</div>

On Wed, Feb 18, 2009 at 05:32:35AM +0100, Jay Kraly wrote:

> I’m running two sets of mongrels using mongrel 1.1.4, one for production  
> one for staging. When executing ‘ps’ from a linux shell, the production  
> mongrels report as expected, however the staging processes are listed as  
> [ruby 18]. The result seems to be that mongrel\_rails cannot stop the  
> staging processes because it doesn’t recognize [ruby18] as a mongrel  
> process.

You could try adding a line like this to the mongrel\_rails script:

$0 = “mongrel\_rails”

That will set the process name.

Mark