Thread: [Cppcms-users] Run cppcms service as daemon

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Hallo,

is there an easy way to run a cppcms service as daemon or do I have to 
implement the double-fork myself?

Thanks,
Julian

It is planned to be implemented (quite soon), but not done yet.

Artyom

----- Original Message ----
> From: Julian Pietron <ju...@wh...>
> To: cpp...@li...
> Sent: Wed, October 13, 2010 3:34:58 PM
> Subject: [Cppcms-users] Run cppcms service as daemon
> 
> Hallo,
> 
> is there an easy way to run a cppcms service as daemon or do I  have to 
> implement the double-fork  myself?
> 
> Thanks,
> Julian
> 
> ------------------------------------------------------------------------------
> Beautiful  is writing same markup. Internet Explorer 9 supports
> standards for HTML5,  CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
> Spend less time writing  and  rewriting code and more time creating great
> experiences on the web.  Be a part of the beta  today.
> http://p.sf.net/sfu/beautyoftheweb
> _______________________________________________
> Cppcms-users  mailing list
> Cpp...@li...
> https://lists.sourceforge.net/lists/listinfo/cppcms-users
> 

Hello All,

Daemonization is implemented in trunk. Together with:

- Switching to unprivileged user and group
- Chrooting to specific directry for extra paranoic users.

See: 

  http://art-blog.no-ip.info/wikipp/en/page/cppcms_1x_config#daemon

for detains.

Of course this is relvant for Unix users and does not
supported on Windows.

> It is planned to be implemented
> (quite soon), but not done yet.
> 
> Artyom
> 
> 
> 
> 
> > Hallo,
> > 
> > is there an easy way to run a cppcms service as daemon
> or do I  have to 
> > implement the double-fork  myself?
> > 
> > Thanks,
> > Julian
> > 

On Wed, 20 Oct 2010 04:51:18 +0800, Artyom  
<art...@ya...> wrote:

> Daemonization is implemented in trunk. Together with:
>
> - Switching to unprivileged user and group
> - Chrooting to specific directry for extra paranoic users.

Would it be even better to also add options "user" and "group" under  
"service.socket" so we can specify something like the following?

service: socket {
	"path": "/tmp/cppcms.socket",
	"user":"www-data",
	"group":"www-data"
}

Regards,

CN

> 
> Would it be even better to also add  options "user" and "group" under  
> "service.socket" so we can specify  something like the following?
> 
> service: socket {
>      "path": "/tmp/cppcms.socket",
>      "user":"www-data",
>      "group":"www-data"
> }

User and group are properties of the process and you can change them only
using forking that is generally done when you daemonize process,
so they have nothing to do with socket.

Also note that TCP sockets (and Unix ones as well) binded before 
switching user to allow for example to listen on port 80 that only
super-user can do. So putting it to "socket" section would be misleading.

Artyom