nhytro at googlemail
Jul 13, 2011, 3:52 AM
Post #5 of 5
Thanks Antonio, must have been blind when I set up the sources :)
Re: Starting sources as a different user?
[In reply to]
On Jul 13, 11:44 am, Antonio Pérez <ape...@skarcha.com> wrote:
> Look the screenshot here. "Execute as user"
> On Wed, Jul 13, 2011 at 11:28 AM, Voltron <nhy...@googlemail.com> wrote:
> > Aha, great, how? I did not find that functionality in the docs. Thanks
> > On Jul 13, 9:57 am, Stefan de Konink <ste...@konink.de> wrote:
> >> On Wed, 13 Jul 2011, Voltron wrote:
> >> > My Python backend sources always write log files in a certain folder
> >> > relative to where they exist. If something happens, and Cherokke has
> >> > to respawn any of the sources, they are run not as the original owner,
> >> > but as the user www-user running Cherokee, that means no rights to
> >> > write the log files anymore and the sources do not start.
> >> > I have modified the logfile directory to allow the www-user to access
> >> > the directory, but I would like to know if it possible to make
> >> > Cherokee respawn the sources using another user.
> >> If the backend is a source, and you make Cherokee spawn it, Cherokee
> >> itself is running as root (but the worker works as www-user), Cherokee can
> >> still spawn the Python script under another user.
> >> Stefan
> >> _______________________________________________
> >> Cherokee mailing list
> >> Chero...@lists.octality.comhttp://lists.octality.com/listinfo/cherokee
> > _______________________________________________
> > Cherokee mailing list
> > Chero...@lists.octality.com
> Antonio Pérez
> Cherokee mailing list
Cherokee mailing list
Cherokee [at] lists