The mailing list for listmasters using Sympa

[Olivier Salaün <address@concealed>]

Hi Troy,

There are many ways of running wwsympa.fcgi processes as user 'sympa'. 
One of them is to usesuexec, other (obsolete) one is to use SetUID bit 
on wwsympa.fcgi, the preferred one is to use Sudo. Please  check Sympa 
documentation to find out how you can make wwsympa work with Sudo.

Troy Davis wrote:

> I'm trying to setup wwsympa on a server that already has a website 
> running on it. The existing site parses all incoming URLs for that 
> domain, so I can't setup wwsympa to run as a Location /sympa as 
> documented.
>
> Instead, I'd like to set it up as sympa.company.com. Here's the 
> relevant section of httpd.conf:
> ...
> FastCgiWrapper /usr/sbin/suexec
> FastCgiIpcDir /tmp/fastcgi
> FastCgiServer /usr/local/sympa-stable/bin/wwsympa.fcgi -processes 3 
> -idle-timeout 120
> ...
> With this configuration, I get the following in the httpd error log:
>
> FastCGI: can't start server "/usr/local/sympa-stable/bin/wwsympa.fcgi" 
> (pid 9288), chdir() failed: Permission denied
>
> I think the problem is that the FastCGI* directives can't be inside 
> the VirtualHost, so httpd attempts to start the fcgi as user apache. 
> All sympa-related files are owned by sympa:sympa, so this obviously 
> isn't going to work. How can I do name-based virtualhosts 
>
> This obviously won't work, does anyone else use a similar approach? If 
> so, how did you get it to work?