Hello, following doc/INSTALL.txt (the quick start) the first command finishes with "Done." which seems to hint at success. However, the INSTALL description says that I will be given a user name and password. This is not the case, nor can I find any point where the procedure is unhappy. Bravely executing the second command ( ./start ) results in a somehow running zope which of course I can not log in. Furthermore, ./start does not return. Environment: Mandrake 6.1, Roxen Any clue? Jan-Oliver Wagner -- Jan-Oliver Wagner http://www.usf.uos.de/~jwagner/ Intevation GmbH Sci. Ass. Inst.of Environmental Systems Res. http://www.usf.uos.de/
Once the Done appears, run the command zpasswd.py: python zpasswd.py -u poppy -p poppy66 access this will set your login to be user - poppy password - poppy66 HTH Phil phil@philh.org -----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of Jan-Oliver Wagner Sent: Thursday, October 14, 1999 2:13 PM To: zope@zope.org Subject: [Zope] Problems installing Zope Hello, following doc/INSTALL.txt (the quick start) the first command finishes with "Done." which seems to hint at success. However, the INSTALL description says that I will be given a user name and password. This is not the case, nor can I find any point where the procedure is unhappy. Bravely executing the second command ( ./start ) results in a somehow running zope which of course I can not log in. Furthermore, ./start does not return. Environment: Mandrake 6.1, Roxen Any clue? Jan-Oliver Wagner -- Jan-Oliver Wagner http://www.usf.uos.de/~jwagner/ Intevation GmbH Sci. Ass. Inst.of Environmental Systems Res. http://www.usf.uos.de/ _______________________________________________ Zope maillist - Zope@zope.org http://www.zope.org/mailman/listinfo/zope (Related lists - please, no cross posts or HTML encoding! To receive general Zope announcements, see: http://www.zope.org/mailman/listinfo/zope-announce For developer-specific issues, zope-dev@zope.org - http://www.zope.org/mailman/listinfo/zope-dev )
Hello,
following doc/INSTALL.txt (the quick start) the first command finishes with "Done." which seems to hint at success. However, the INSTALL description says that I will be given a user name and password. This is not the case, nor can I find any point where the procedure is unhappy.
I have had the same anomaly on Mandrake 6.0. The installation is successful the install script just fails to generate a password. I fixed that by using the zpasswd.py script. The following output shows how I used it. hallam$ cd /usr/local/zope hallam$ export PYTHONHOME=/usr/local/zope hallam$ bin/python zpasswd.py ~/access Username: mark Password: mark Verify password: mark Please choose a format from: SHA - SHA-1 hashed password CRYPT - UNIX-style crypt password CLEARTEXT - no protection. Encoding: SHA Domain restrictions: Just hit enter when asked for domain restrictions. That will create a login id with manager permissions and no domain restrictions. Good luck!
Bravely executing the second command ( ./start ) results in a somehow running zope which of course I can not log in. Furthermore, ./start does not return.
./start directly executes the Zope command in the foreground, so ./start doesn't return until Zope is killed. Does anyone else know how to work around this? -- martinja@ice-works.com All opinions expressed are my own and not necessarily those of my employer unless otherwise noted.
On Thu, Oct 14, 1999 at 09:52:56AM -0400, Joseph A. Martin wrote:
./start directly executes the Zope command in the foreground, so ./start doesn't return until Zope is killed. Does anyone else know how to work around this?
I have a boot script for my Debian distro that starts Zope on boot and shuts it down. /etc/init.d/zope --------------------- #! /bin/sh # # zope Start/Stop Zope. ;) # NAME=zope PATH=/bin:/usr/bin:/sbin:/usr/sbin ZOPEHOME=/home/rcm/devel/zope/zope ZOPELOGFILE="$ZOPEHOME/var/Z2.log" ZOPEOPTS="-z $ZOPEHOME -t 10" case "$1" in start) echo Starting Zope... su rcm -c "${ZOPEHOME}/start ${ZOPEOPTS} > ${ZOPELOGFILE} 2>&1 &" ;; stop) echo Stopping Zope... su rcm -c "${ZOPEHOME}/stop" ;; restart) echo Restarting Zope... su rcm -c "${ZOPEHOME}/stop" su rcm -c "${ZOPEHOME}/start ${ZOPEOPTS} > ${ZOPELOGFILE} 2>&1 &" ;; force-reload) echo force-reload option not yet implemented!! ;; *) echo "Usage: /etc/init.d/$NAME {start|stop|restart|force-reload}" exit 1 ;; esac exit 0 --------------------- Hope it helps Rafa C. Marcos -- Linux. The Choice of a GNU Generation! -> http://www.debian.org
At 15:13 14/10/99 , Jan-Oliver Wagner wrote:
Hello,
following doc/INSTALL.txt (the quick start) the first command finishes with "Done." which seems to hint at success. However, the INSTALL description says that I will be given a user name and password. This is not the case, nor can I find any point where the procedure is unhappy.
Bravely executing the second command ( ./start ) results in a somehow running zope which of course I can not log in. Furthermore, ./start does not return.
Environment: Mandrake 6.1, Roxen
The fact that the start command doesn't return, is because that file by default uses the -D switch of Zope, which stands for Debug. One side effect is that it stays attached to the terminal. Edit start and remove the -D and it will be more daemonic. What command did you run? I find it strange no password was communicated. Maybe you should scroll back a bit. The password is stored in a file called 'access', in the Zope root. You can generate a new access file with the following command, issued in the Zope root dir: /path/to/python zpasswd.py access It will prompt you for a username, password, encryption method and optional domain specification (which is a space separated list of ip address and ip numbers with ot without wildcards). If you use zpasswd.py without any arguments, you'll get a help message: /path/to/python zpasswd.py -- Martijn Pieters, Web Developer | Antraciet http://www.antraciet.nl | Tel: +31-35-7502100 Fax: +31-35-7502111 | mailto:mj@antraciet.nl http://www.antraciet.nl/~mj | PGP: http://wwwkeys.nl.pgp.net:11371/pks/lookup?op=get&search=0xA8A32149 ------------------------------------------
Martijn Pieters wrote:
What command did you run? I find it strange no password was communicated.
Some changes were made to the installer to make sure permissions are sane, this is done after the password generation so the password scrolls off the screen. We'll fix it. -Michel
participants (6)
-
Jan-Oliver Wagner -
Joseph A. Martin -
Martijn Pieters -
Michel Pelletier -
Phil Harris -
Rafael Cordones Marcos