10 More Discussions You Might Find Interesting
1. Windows & DOS: Issues & Discussions
Hi Team,
My new build configuration always looking for the files from the build where i copied from.
please help me to resolve this.
I am using Visual studio 2008.It has Qt 4.8. plugins,qml,C++ development
I created new debug_new build configuration with additional preprocessor from the... (1 Reply)
Discussion started by: SA_Palani
1 Replies
2. Web Development
Hi,
I'm new to developing modules for Apache. I understand the basics now and can develop something simple which allows a 'GET' request to happen, but what I want to do is actually 'POST' information to my site. I know the basic POST Request works and I can see that it is post by looking at... (2 Replies)
Discussion started by: fishman2001
2 Replies
3. Shell Programming and Scripting
Hi
I have a build.xml file and I can run it on Windows via cmd. Now I want to write a script to invoke the same. Is there a way to do this? (1 Reply)
Discussion started by: ankur328
1 Replies
4. UNIX for Dummies Questions & Answers
Hi,
So I downloaded this kernel source and was able to build it successfully.
But I want to add this SDK source code inside, can anyone help me how to do this? Note that the SDK source can be built by itself.
I added the SDK in the main Makefile:
init-y := init/
#added SDK... (0 Replies)
Discussion started by: h0ujun
0 Replies
5. Solaris
Hi,
Generally we will run to install, configure apache 2.x on Solaris machine, but dont want to follow these on the remaining machines.
I want to build the apache binary centrally, so that i can untar the tar file on remaining machines. Please suggest on how to prepare this file and when i... (12 Replies)
Discussion started by: prash358
12 Replies
6. Web Development
Hello ,
I have s Solaris 10 10/09 s10x_u8wos_08a X86 OS.
I installed Apache 1.3.34 and MYSQL 5.1.50.
while executing the following command to compile the mod_auth_mysql.c module
sudo ./apxs -c -L/d00/tbls/mysql/lib -I/d00/tbls/mysql/include -lmysqlclient -lm -lz mod_auth_mysql.c.
result of it... (2 Replies)
Discussion started by: cnighojkar
2 Replies
7. UNIX for Advanced & Expert Users
hi folks,
Can you help me how to dump CFTOKEN and CFID requests in apache access_log ?
can you give me a better idea how to accomplish this ?
thanks (2 Replies)
Discussion started by: linuxgeek
2 Replies
8. UNIX for Advanced & Expert Users
Hi,
I have web server (apache) installed in server-1 and i want to view the web pages from diferent servers also while the web server is running only in one server ....(all the servers are connected to office LAN)
right now all the servers have apache running......and CPU utilzation is at its... (2 Replies)
Discussion started by: aditya.ece1985
2 Replies
9. Solaris
I am trying to build 64 bit apache 2.2.4 on a Sun server. I have built many
applications so far. This is my configure line
CC='gcc -m64 -mcpu=v9 -O3' ./configure --disable-ipv6 --enable-info --enable-status
--enable-ssl --with-ssl=/usr/local/ssl --disable-negotiation --disable-userdir ... (2 Replies)
Discussion started by: csross
2 Replies
10. UNIX for Dummies Questions & Answers
Hi,
I have the following simple CGI script, just containg header:
#!/usr/bin/perl -w
use CGI ':standard';
use lib "/home/myname/lib/perl5/site_perl/5.8.5/";
use Mail::Sendmail;
I also have included this directive in ~/public_html/.htaccess :
SetEnv PERL5LIB... (0 Replies)
Discussion started by: monkfan
0 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)