Set process name to 'prosody' when running

[GoogleCodeExporter]

Currently process name is 'lua', though I'm sure it is possible to change
at runtime, need to look into it.

Original issue reported on code.google.com by MWild1 on 11 Apr 2009 at 11:21

[GoogleCodeExporter]

Removing milestone, this apparently can't be done in any sensible way, but 
still...

Original comment by MWild1 on 5 May 2009 at 4:14

• Removed labels: Milestone-0.4.1

[GoogleCodeExporter]

I don't know if you've considered this or how feasible it is, but how about a 
small
wrapper written in C whose only purpose is to load the Lua interpreter and 
execute
the main prosody script? The C wrapper could then be /usr/bin/prosody and what's
/usr/bin/prosody now could be /usr/lib/prosody/core/main.lua or something like 
that.

Having a unique process name would certainly make writing daemon scripts easier.

Original comment by goo...@dbb.io on 11 May 2009 at 4:16

[GoogleCodeExporter]

I've been toying around with that last idea and came up with the file attached. 
It's
basically just a copy n' paste from an embedded Lua guide but it seems to work 
as far
as starting the server and having it accept connections. My testing went as far 
as
running it on my laptop, creating two accounts, and having them talk to each 
other.

I'm sure it would have to be more complex to handle things like POSIX signals, 
etc.
but it seems like a workable solution since Prosody already has some components
written in C, correct?

Original comment by goo...@dbb.io on 12 May 2009 at 1:46

Attachments:

• prosodyw.c