Thanks. I sorted it out using ./zopectl adduser.<br><br><div><span class="gmail_quote">On 9/30/05, <b class="gmail_sendername">Chris Withers</b> <<a href="mailto:chris@simplistix.co.uk">chris@simplistix.co.uk</a>> wrote:
</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">michael nt milne wrote:<br>> Anyway I've followed all the instructions in security.txt
, telnetting<br><br>stop right there... you should be using ssh...<br><br>> in as<br>> the user that made the zopeinstance and running<br>> python zpasswd.py access<br>> using SHA-1 and then entering nothing for domains ( I presumed that this
<br>> would give access for all domains etc)<br><br>correct.<br><br>> I then get an access denied message on running this and the access file is<br>> not created.<br><br>well, maybe you could show us the error rather than not quite giving us
<br>enough information to be able to help you ;-)<br><br>guesses:<br><br>- your user didn't have permission to read or maybe execute python or<br>zpasswd.py<br><br>- your user didn't have permissions to write to the directory where you
<br>were trying to create the access file.<br><br> > Yes, the access file was being created in the homeinstance.<br><br>But yet you said above it wasn't created a all?!<br><br> > One thing I<br> > didn't do was run the
zpasswd.py file when zope was stopped though,<br>as I did<br> > with ./zopectl<br><br>zope doesn't need to be stopped, but it does need to be restarted once<br>the access file has been created...<br><br>that said, if you want zopectl to let you do things without stopping
<br>Zope, just get a ZEO setup up and running...<br><br>cheers,<br><br>Chris<br><br>--<br>Simplistix - Content Management, Zope & Python Consulting<br> - <a href="http://www.simplistix.co.uk">http://www.simplistix.co.uk
</a><br></blockquote></div><br>