anyone fairly experienced with Apache??? Document Root Fiddling?
Quote:
Originally Posted by glen.barber
This doesn't answer your 'My Solution' question, but I do something similar on a development machine. I use subversion to checkout from my code repository into /home/me/svn/site and create a symbolic link for apache to this location:
I actually considered using a link. I don't know why, but I just assumed that apache wouldn't play well with a link.
Quote:
Originally Posted by glen.barber
I know it doesn't answer your real question, but maybe this solution is easier. *shrug*
Well, this could be a work around. The only problem/reason its a work around and not a solution is because I actually have 24 GB of data inside my development folders on a couple computers. such a large development folder brings about two problems here:
my dropbox account doesn't have that much of storage (nor would I want it syncing that stuff anyway)
whenever running my login's "switch-server's-location" script, it would have to move the 24 GB of stuff out of /var/www just for the link to work.
I'll probably use link to redirect Apache just on a computer or two right now, but I'll still be searching for a more thorough solution. Thanks again, glen.barber, I appreciate the input.
Perhaps someone with a better understanding of Apache than me could explain to me "Apache's http root isn't meant to be fiddled with"? and such an undertaking isn't for the inexperienced?
Currently our Apache log files are huge, I want to put say a month's time limit on this, then when it hits the end of the month I would like it to start over writing.
Does anyone know where the config file is for this and what its called? I also want to do exactly the same on wtmp config (who... (1 Reply)
Hi, I need a script that will:
1. Go through about 20 different folders, each containing about 20 1d files. The 1d files go something like this:
22.253 37.707 78.117 112.374 127.944 156.067 180.956 233.785 249.256 ... (1 Reply)
Hi I am new to shell scripting. There is a requirement to write a shell script to meet follwing needs.Prompt reply shall be highly appreciated.
script that will compare two config files and produce 2 outputs - actual config file and a report indicating changes made.
OS :Susi linux ver 10.3.
... (4 Replies)
Hello dear users, here I have a script to manipulate .csv files that are like this originally:
And I need to make a script to delete certain fields. Each field is separated with a comma.
So, here is my script (at least a part of it):
Field $1 is composed of a name, and then a... (5 Replies)
Hi folks,
I am trying to configure Apache webserver and also a virtual host inside this webserver.
For Global server config: /var/www/html/index.html
For virtual host config: /var/www/virtual/index.html
Both client10 & www10 are pointing to 192.168.122.10 IP address.
BUT, MY... (1 Reply)
Our Apache log files are written to a location on the server that we as clients have no access. Don't ask.
Every month, I have to e-mail the administrator to have him manually copy our Apache log files to a directory in our file space. You can probably guess how efficient it is to do things this... (3 Replies)
#!/bin/bash
#
name=$1
type=$2
number=1
for file in ./**
do
if
then
filenumber=00$number
elif
then
filenumber=0$number
fi
tempname="$name""$filenumber"."$type"
if (4 Replies)
I am trying to automate editing of a json file using bash script.
The file I initially receive is
{
"appMap": {
"URL1": {
"name": "a"
},
"URL2": {
"name": "b"
},
"URL3": {
"name": "c"
},
}
WHat I would like to do is replace... (5 Replies)
I just want to make sure I am understanding how to pass a config file to a bash script . In the below I pass to arguments to a script, then define them in the script as id and config. I then source config using ., if I understand correctly the variables in the config file can now be used by the... (11 Replies)
Discussion started by: cmccabe
11 Replies
LEARN ABOUT DEBIAN
gsexec
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)