From: Nick J. <nk...@ia...> - 2003-04-25 19:10:58
|
On Fri, Apr 25, 2003 at 11:59:16AM -0700, Bryce Harrington wrote: > > Sure thing, here we go: > > Script started on Fri Apr 25 11:54:00 2003 [*snip*] > ---------------------- > Installation complete! > ---------------------- > [root@sherborne sandweb]# exit > {bryce@sherborne} ~/src/sandweb (5): ls bin > CVS sandweb-admin sandweb.cgi sandweb-editor sandweb-expect sandweb-ssh > {bryce@sherborne} ~/src/sandweb (6): sandweb-admin --add-user bryce > Enter password for bryce: > Unable to open /usr/local/share/sandweb/data/passwd : Permission denied > {bryce@sherborne} ~/src/sandweb (7): su > Password: > [root@sherborne sandweb]# sandweb-admin --add-user bryce > unable to open config file: ../etc/sandweb.cfg > return data: <pre>$VAR1 = { > 'errlev' => 0, > 'data' => {} > }; > </pre>[root@sherborne sandweb]#>[root@sherborne sandweb]# exit > {bryce@sherborne} ~/src/sandweb (8): > Script done on Fri Apr 25 11:56:43 2003 Ok, two things here (these need to be documented until we figure out a way to resolve them). 1. If a 'which sandweb-admin' shows the file residing in /usr/bin, this is not good. Delete the sandweb-admin script in /usr/bin. Seems in some cases (we aren't sure exactly why it varies) the Makefile puts it there automatically because it is registered as a binary. However we manually put it in /usr/local/bin/sandweb-admin and it's this one that has the config file changes, etc, added to them. Based on your output though (it's not complaining about not being able to find a config file in ../etc) it seems as if you are running the one in /usr/local/bin. 2. Always create sandweb user accounts su'd as the webserver user (in your case apache). It looks like this isn't documented in the README, and I'm not sure why. The permissions need to be set as the webserver user. Ok, so other than that, the install looks good. So what happens when you access the cgi for the first time? (it would help probably to turn debug on in the /usr/local/etc/sandweb/sandweb.cfg). - Nick |