1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
|
<TITLE>CGIWrap - Usage with AFS</TITLE>
<CENTER><H2>CGIWrap - Usage with AFS</H2></CENTER>
<HR>
<P>
CGIwrap will work with AFS, with at least the following directory permissions:
<P>
<CENTER><TABLE BORDER=1 WIDTH=50%>
<TR><TH>Dir</TH>
<TH>User/Group</TH>
<TH>Permissions</TH></TR>
<TR><TD ALIGN=LEFT>~</TD>
<TD ALIGN=CENTER>system:anyuser</TD>
<TD ALIGN=CENTER>l</TD></TR>
<TR><TD ALIGN=LEFT>~/public_html</TD>
<TD ALIGN=CENTER>system:anyuser</TD>
<TD ALIGN=CENTER>l</TD></TR>
<TR><TD ALIGN=LEFT>~/public_html</TD>
<TD ALIGN=CENTER>system:anyuser</TD>
<TD ALIGN=CENTER>rl</TD></TR>
</TABLE></CENTER>
<P>
If you are running httpd authenticated to AFS, you can replace
system:anyuser above with that userid.
<P>
If you are using CGIWrap with AFS I'd suggest making sure to enable the
AFS PAG support in the Configure script. This automatically creates a PAG
for any script that is launched, that way if the script klogs, it won't
affect the server or other scripts. When using cgiwrap with AFS based
accounts, you need to keep in mind that scripts are run un-authenticated.
This means that any files that are accessed will be accessed as
<TT>system:anyuser</TT>. In general, this means that the script will not
have write access to your directory.
|
