On Thu, Jul 8, 2010 at 10:09 PM, Paul Dlug <[email protected]> wrote:
> On Thu, Jul 8, 2010 at 5:42 PM, Eric Wong <[email protected]> wrote:
>> Devin Ben-Hur <[email protected]> wrote:
>>> On 7/8/10 1:55 PM, Paul Dlug wrote:
>>>> Is there a way to set an application name for unicorn processes?
>>>> Basically an arbitrary name which would then show up in the process
>>>> list to identify unicorn processes, like what thin does with --tag.
>>>
>>> A patch to do something like that was recently rejected. Instead the
>>> documentation was updated with Eric's recommendated solution to instance
>>> identification:
>>> http://rubyforge.org/pipermail/mongrel-unicorn/2010-July/000620.html
>>>
>>> + Using an absolute path for for CONFIG_FILE is recommended as it
>>> + makes multiple instances of Unicorn easily distinguishable when
>>> + viewing ps(1) output.
>>
>> Lawrence Pit also recommends running each app as a separate user,
>> which is also a great idea (IMHO, though some ops people I know
>> dislike this):
>>
>> http://mid.gmane.org/[email protected]
>
> I think both of these solutions are undesirable, relying on the config
> file path is not ideal and running with different users is practical
> in my environment. Both these point out the need for some feature to
> distinguish running applications, I think adding a configurable
> application name/tag would be very useful, not sure how much work it
> would be but I can look at adding a patch if there is interest.
The patch was already submitted and rejected. If you want this
feature, you can implement it yourself in the config file with the
following code:
class Unicorn::HttpServer
def proc_name(tag)
$0 = ([ File.basename(START_CTX[0]), "application name/tag",
tag ]).concat(START_CTX[:argv]).join(' ')
end
end
Jeremy
_______________________________________________
Unicorn mailing list - [email protected]
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
