"Fossies" - the Fresh Open Source Software Archive

Member "cgiwrap-4.1/htdocs/afs.html" (16 Jun 2008, 1288 Bytes) of package /linux/www/old/cgiwrap-4.1.tar.gz:

As a special service "Fossies" has tried to format the requested source page into HTML format using (guessed) HTML source code syntax highlighting (style: standard) with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file.

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