[Zope-dev] call file.update-data question

2002-05-20 Thread ch j liu

hello ,everybody.

when I call file.update_data function ,zope need
authenticate. even though I check all permission to a
new user,but the user can not login .why ,what should
I do ?
thanks .
zope 2.5.1 win2k professional

__
Do You Yahoo!?
LAUNCH - Your Yahoo! Music Experience
http://launch.yahoo.com


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



Re: [Zope-dev] Zope crash & restart

2002-05-20 Thread Jens Vagelpohl

> I did. What is standard procedure if the situation like the one I've met 
> appears? What is scenarion from bug report to product release without the 
> bug found?

i don't know. the people on the python-dev mailing list could help you with 
that question.

jens



___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



Re: [Zope-dev] Zope/Python crashing

2002-05-20 Thread Myroslav Opyr

Matthew T. Kromer wrote:

> Myroslav Opyr wrote:
>
>> For FreeBSD there is another pthreads related bug in Python. And 
>> quick-patch from 
>> https://sourceforge.net/tracker/?func=detail&aid=554841&group_id=5470&atid=305470 
>> with THREAD_STACK_SIZE=0x2 solves the problem. But it is quick 
>> and dirty hack. Will it be solved in next bugfix release of Python? 
>> Whom/where I have to contact to have progress regarding the issue?
>>
>> I'll post comment into SF tracker because site which crashed 
>> previously works fine now (for 5 days already)... Is that sufficient? 
>> This dirty patch is not acceptable and clean solution have to take 
>> place. Should I take part and try to develop one?
>
> Well, the way you start threading with pthreads requres a single 
> initializer for the stack size; once you have initialized the 
> threading environment you cannot change the stacksize later, to the 
> best of my knowledge. 

Ok. What general solution should be? One of the possible ways would be 
to reserve big stack enough for all cases but only small portion of it 
(generally used by apps) turn into phisical memory. It should be default 
behavior for majority of OSes/Libs, shouldn't it?

> I suppose you could finesse a new python startup argument, or 
> environment variable check. 

+1 for startup argument
-1 for environment

> I think the SF tracker is the best way to approach that. 

You mean discussion about the issue shoud take place in tracker?

m.
-- 
Myroslav Opyr
zope.net.ua  ° Ukrainian Zope Hosting
e-mail: [EMAIL PROTECTED] 
cell: +380 50.3174578






___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



Re: [Zope-dev] Zope crash & restart

2002-05-20 Thread Myroslav Opyr

Jens Vagelpohl wrote:

> add your comment, encouragement, flames et to the sourceforge bug 
> tracker issue. i guess that would help most. 

I did. What is standard procedure if the situation like the one I've met 
appears? What is scenarion from bug report to product release without 
the bug found?

m.

> jens
>
> On Wednesday, May 15, 2002, at 10:55 , Myroslav Opyr wrote:
>
>> Hi,
>>
>> it look like it works! I have to give site some time to run to be sure.
>>
>> Where I can vote for a bug or to give comments? On SF.tracker issue? to
>> make it go into release.
>>
>> As far as I understand the patch is quick-hack to make it work and do 
>> not
>> solve the issue completely, just increase the stack size... There should
>> be better solution, isn't it?
>>
>> Will it go into Python-2.1.4?
>>
>> m.
>> -- 
>> Myroslav Opyr
>> zope.net.ua * Ukrainian Zope Hosting
>> e-mail: [EMAIL PROTECTED]
>> cell: +380 50.3174578
>>
>> On Wed, 15 May 2002, Behrens Matt - Grand Rapids wrote:
>>
>>> Myroslav Opyr wrote:
>>>
 As far as I remember the issue was solved in Python 2.1.3, wasn't 
 it? Or
 it was GC patch?
>>>
>>> No.
>>>
>>> Try my patch, that solves the problem Jens is talking about. 
>>
-- 
Myroslav Opyr
zope.net.ua  ° Ukrainian Zope Hosting
e-mail: [EMAIL PROTECTED] 
cell: +380 50.3174578






___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



[Zope-dev] Zope 2.5.1 RPM built and ready for testing

2002-05-20 Thread Adam Manock

I have built a Zope 2.5.1 source RPM, it's ready for community tasting and 
testing ;-)

Zope Corp, could you please host it, perhaps at 
http://www.zope.org/Products/Zope/2.5.1 ?

I would like to only make it available in .src.rpm format initially, so 
that users & testers can "rpmbuild --rebuild" it and test it as is, or "rpm 
-Uvh" it, look over the installed spec, scripts etc, make changes (please 
let me know!) and finally "rpmbuild -ba" the spec.

When any and all changes are in I can build a "final" .src.rpm, this would 
also be the time to make binary RPMS available.

Eventually, I'd like to put the spec, scripts etc into Zope's CVS, so that 
"rpmbuild -ta Zope.tar.gz" could be used to generate rpms directly from 
tarball, as retrieved by: 
"http://cvs.zope.org/Zope/Zope.tar.gz?tarball=1&only_with_tag=Zope-2_5-branch"; 
for example. This part might take a while, I looked at what was done in the 
spec of courier-imap-1.4.5.tar.gz and it seems to be a fairly involved 
task... It may be best to wait for InstallationAndConfiguration of 
Proposals to be implemented for the default build / install of Zope before 
attempting to dynamically wrap this process with RPM.

Questions, comments, suggestions, patches, changes, feedback etc are 
welcome and encouraged.

Adam



___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



[Zope-dev] Strange crash/startup error

2002-05-20 Thread Scott Burton
Hello, recently my Zope install of 2.5.1 had crashed and will not start back up. Everything was working while I was testing an external method. After I ran another test, Zope stopped responding. I looked on the server and the service was still running. I tried to restart and got this error. http://photos.groups.yahoo.com/group/zope/vwp?.dir=/&.src="gr&.dnm=Error.GIF&.view=t&.done=http%3a//photos.groups.yahoo.com/group/zope/lst%3f%26.dir=/%26.src=gr%26.view=t I hope the link works cause it is a yahoogroups photo. Basically the TB says: HTTPResponse.py line 91, start_of_header_search = re.compile... module object has no attribute "compile"
I have ran fsrecover, re-installed Zope, ran a repair on ActivePython 2.2.1. But still it crashes with this error. I did notice that the fresh install ran fine with the standard products and data.fs. Help me please!
Zope2.5.1, ActivePython 2.2.1 build 222, Windows 2000 serverDo You Yahoo!?
LAUNCH - Your Yahoo! Music Experience

Re: [Zope-dev] Zope/Python crashing

2002-05-20 Thread Matthew T. Kromer

Myroslav Opyr wrote:

>
> For FreeBSD there is another pthreads related bug in Python. And 
> quick-patch from 
> https://sourceforge.net/tracker/?func=detail&aid=554841&group_id=5470&atid=305470 
> with THREAD_STACK_SIZE=0x2 solves the problem. But it is quick and 
> dirty hack. Will it be solved in next bugfix release of Python? 
> Whom/where I have to contact to have progress regarding the issue?
>
> I'll post comment into SF tracker because site which crashed 
> previously works fine now (for 5 days already)... Is that sufficient? 
> This dirty patch is not acceptable and clean solution have to take 
> place. Should I take part and try to develop one?


Well, the way you start threading with pthreads requres a single 
initializer for the stack size; once you have initialized the threading 
environment you cannot change the stacksize later, to the best of my 
knowledge.

I suppose you could finesse a new python startup argument, or 
environment variable check.

I think the SF tracker is the best way to approach that.

-- 
Matt Kromer
Zope Corporation  http://www.zope.com/ 





___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )