-bash-3.00$ ls -l
total 24
drwxr-xr-x 2 spam spam 4096 Aug 21 04:37 bin
drwxr-xr-x 3 spam spam 4096 Aug 23 15:43 config
drwx------ 2 spam spam 4096 Aug 21 09:05 private
drwxr-xr-x 7 spam spam 4096 Aug 23 15:41 public_html
drwxr-xr-x 2 spam spam 4096 Aug 23 15:47 scripts
drwx------ 2 spam spam 4096 Aug 21 04:33 sess
-bash-3.00$ cd public_html/
-bash-3.00$ ls -l
total 84
lrwxrwxrwx 1 spam spam 11 Aug 21 09:29 admin.pl -> cannibal.pl
-rwxr-xr-x 1 spam spam 34814 Aug 22 21:57 cannibal.pl
drwxr-xr-x 2 spam spam 4096 Aug 21 04:33 docs
-rw-r--r-- 1 spam spam 318 Apr 15 2004 favicon.ico
drwxrwxrwx 2 spam spam 4096 Aug 21 04:33 flags
drwxr-xr-x 2 spam spam 4096 Apr 24 10:09 images
drwxr-xr-x 2 spam spam 4096 Apr 24 10:09 incl
-rw-r--r-- 1 spam spam 502 Aug 22 22:02 index.html
-rwxr-xr-x 1 spam spam 92 Aug 23 03:32 rocks.pl
-rwxr-xr-x 1 spam spam 14207 Aug 21 09:31 spam_report.pl
drwxrwxrwx 2 spam spam 4096 Aug 21 04:33 tmp
-bash-3.00$
The permissions on cannibal.pl are 755. As far as I know, that
should be readable.
[r...@web conf.d]# cat perl.conf
#
# Mod_perl incorporates a Perl interpreter into the Apache web server,
# so that the Apache web server can directly execute Perl code.
# Mod_perl links the Perl runtime library into the Apache web server
# and provides an object-oriented Perl interface for Apache's C
# language API. The end result is a quicker CGI script turnaround
# process, since no external Perl interpreter has to be started.
#
LoadModule perl_module modules/mod_perl.so
<Directory /usr/local/spamcannibal/public_html>
setHandler perl-script
PerlResponseHandler ModPerl::Registry
PerlOptions +ParseHeaders
Options +ExecCGI
Order allow,deny
Allow from all
</Directory>
[r...@web conf.d]#
http://web.robinson-west.com/~spam/rocks.pl
The above URL works. Try and trim it down to just ../~spam/ and I get
the error:
[Mon Aug 23 22:52:36 2010] [error] [client 192.168.5.82] Attempt to
serve directory: /usr/local/spamcannibal/public_html/
Of course, if you try to access this over the Internet the error will be
different ;-)
...
enabling admin management on user admin web page
Admin management is enabled by default by the installation procedure.
The sticky bit on the sc_session.pl file is used as a flag to
enable/disable admin management support. With admin management disabled,
you must add and delete administrative user from the private/passwd file
using a text editor. New users may be added with a blank password.
i.e. fred:
To admin access to allow admins to add and delete users, login as the
spamcannibal user and type this:
cd scripts
./sc_session.pl admin on
to restrict access so that admin users must be added and removed by
hand,
./sc_session.pl admin off
-bash-3.00$ scripts/sc_session.pl admin on
Could not open config file
...
Any thoughts on why the config file sc_web.conf can't be opened???
I suspected the inability to open this file is somehow connected to why
the web page doesn't render either.
I am totally lost and the documentation on this is abysmal.
_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug
