Sponsored Content
Top Forums Web Development Unable to start the apache web server Post 302896115 by bartus11 on Friday 4th of April 2014 11:57:00 AM
Old 04-04-2014
I just noticed that you are trying to start apache as a user other than "root". Do you have root access to that machine?
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Apache Web Server

Hi, Can someone help me for the Apache Web Server files for HP-UX 11.0 systems. Is there any download available? Thanks in Advance Anent (9 Replies)
Discussion started by: anent
9 Replies

2. Solaris

Apache web server question

Hi - Maybe not the right forum for this but I will ask anyway.. I recently installed apache on my ultra 10 - solaris 9... Working okay - and I have some docs in my htdocs directory that I can access through a web browser.. Now I want to get a bit fancy and change the home page so I can... (2 Replies)
Discussion started by: frustrated1
2 Replies

3. Red Hat

How to start the right instance of Apache on RedHat server

Hi, I have 2 apache instance on my machine (RedHat), and i need to start the "apache2" after any reboot but could not find the way ( searching into "httpd.conf" ), so i'am starting "apache2" manually. After a reboot, none of them starts and when i when doing : httpd -k start, i got "apache"... (14 Replies)
Discussion started by: mehdi1973
14 Replies

4. Solaris

Uninstall Apache web server

Hello, I have a Solaris 10 and it looks like it was installed with apache. I see some files in: Since I'd like to use CSWapache2 from OpenCSW I'd like to remove the one from SUN but I don't know which package name it has. Do you know how can I remove it ? Thanks R.F ---------- Post... (4 Replies)
Discussion started by: RobertFord
4 Replies

5. Web Development

Apache Web Server Config

Hi Gurus I am a newbie in Apache. I want to configure Apache Web server(A for reference) to receive all requests on Port-843 to be redirected to another Apache web server(B) and access a crossdomain.xml(located in /var/www/html) file there. I have put the following entries in... (0 Replies)
Discussion started by: Hari_Ganesh
0 Replies

6. HP-UX

Apache web server instalation error in HP-UX 11.31

Hi , I am getting an error while installing on a new hp-ux 11.31 server for the first time. I have troubleshooted to some extent and installed the C compiler which it was asking for and now a new error has arised. please find the below error, Any help would be appreciated. $ make Making all... (1 Reply)
Discussion started by: Prasad@hp-ux
1 Replies

7. Web Development

Apache 2.4 web server - string manipulation

Hi, I have configured an Apache 2.4 web server for Kerberos authentication. I need to pass the user in an HTTP header to the back-end server. This can be achieved by:- # Set header to blank RequestHeader set KERBEROS_USER "" # Set header RequestHeader set KERBEROS_USER "%{REMOTE_USER}s"... (0 Replies)
Discussion started by: sniper57
0 Replies

8. Shell Programming and Scripting

Need help getting a web page to start a server.

Wont let me add the solved tag, say's im over the max. Removing 2 tags did not help. No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial One of my game servers keeps going offline and so I want to... (18 Replies)
Discussion started by: Stuperfied
18 Replies
GSEXEC(8)							  GridSite Manual							 GSEXEC(8)

NAME
gsexec - Switch user before executing external programs SYNOPSIS
gsexec [-V] SUMMARY
gsexec is used by the Apache HTTP Server to switch to another user before executing CGI programs. In order to achieve this, it must run as root. Since the HTTP daemon normally doesn't run as root, the gsexec executable needs the setuid bit set and must be owned by root. It should never be writable for any other person than root. gsexec is based on Apache's suexec, and its behaviour is controlled with the Apache configuration file directives GridSiteExecMethod and GridSiteUserGroup added to Apache by mod_gridsite(8) Four execution methods are supported: nosetuid, suexec, X509DN and directory, and these may be set on a per-directory basis within the Apache configuration file. NOSETUID METHOD
This is the default behaviour, but can also be produced by giving GridSiteExecMethod nosetuid CGI programs will then be executed without using gsexec, and will run as the Unix user given by the User and Group Apache directives (nor- mally apache.apache on Red Hat derived systems.) SUEXEC METHOD
If GridSiteExecMethod suexec is given for this virtual host or directory, then CGI programs will be executed using the user and group given by the GridSiteUserGroup user group directive, which may also be set on a per-directory basis (unlike suexec's SuexecUserGroup which is per-server only.) The CGI program must either be owned by root, the Apache user and group specified at gsexec build-time (normally apache.apache) or by the user and group given with the GridSiteUserGroup directive. X509DN METHOD If GridSiteExecMethod X509DN is given, then the CGI program runs as a pool user, detemined using lock files in the exec mapping directory chosen as build time of gsexec. The pool user is chosen according to the client's full certificate X.509 DN (ie with any trailing GSI proxy name components stripped off.) Subsequent requests by the same X.509 identity will be mapped to the same pool user. The CGI program must either be owned by root, the Apache user and group specified at gsexec build-time (normally apache.apache) or by the pool user selected. DIRECTORY METHOD
If GridSiteExecMethod directory is given, then the CGI program runs as a pool user chosen according to the directory in which the CGI is located: all CGIs in that directory run as the same pool user. The CGI program must either be owned by root, the Apache user and group specified at gsexec build-time (normally apache.apache) or by the pool user selected. EXECMAPDIR
The default exec mapping directory is /var/www/execmapdir and this is fixed when the gsexec executable is built. The exec mapping directory and all of its lock files must be owned and only writable by root. To initialise the lock files, create an empty lock file for each pool user, with the pool username as the filename (eg user0001, user0002, ...) As the pool users are leased to X.509 identities or directories, they will become hard linked to lock files with the URL-encoded X.509 DN or full directory path. You can recycle pool users by removing the corresponding URL-encoded hard link. stat(1) and ls(1) with option -i can be used to print the inodes of lock files to match up the hard links. However, you must ensure that all files and processes owned by the pool user are deleted before recycling! OPTIONS
-V If you are root, this option displays the compile options of gsexec. For security reasons all configuration options are changeable only at compile time. MORE INFORMATION
For further information about the concepts and the security model of the original Apache suexec please refer to the suexec documentation: http://httpd.apache.org/docs-2.0/suexec.html For examples using the gsexec extensions, please see the GridSite gsexec page: http://www.gridsite.org/wiki/Gsexec AUTHORS
Apache project, for original suexec Andrew McNab <Andrew.McNab@manchester.ac.uk> for gsexec modifications. gsexec is part of GridSite: http://www.gridsite.org/ SEE ALSO
httpd(8), suexec(8), mod_gridsite(8) gsexec October 2005 GSEXEC(8)
All times are GMT -4. The time now is 12:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy