Hi again,
I just changed from SysVSemaphoreLocker to NULLLocker. I'll inform you how
this changed affected %udat when it has been in use for some time.
The system is currently under development and will be used in business.
There will be a considerable load on the system once it is launched.
I believe your concern behind your question relating to the number of page
requests that the system is under is that with no locking mechanism and a
high degree of cuncurrent requests might not be the best of combinations.
Thanks once again for your support.
regards
ragnar
-----Original Message-----
From: Gerald Richter [mailto:[EMAIL PROTECTED]]
Sent: 10 May 2000 20:53
To: Ragnar Hakonarson; [EMAIL PROTECTED]
Subject: RE: problems with %udat persistance
> That leaves us with the SysVSemaphoreLocker mechanism as
> the prime suspect, or?
>
I also use mysql as session database on a Linux system and it works without
problems..., but from what you describe it really looks like a Locker
problem, so I would first try to use NullLocker instead of
SysVSemaphoreLocker. Has your system many page requests or is it just a test
system?
> Am I completely on the wrong track?
>
No, surely not
Gerald
-------------------------------------------------------------
Gerald Richter ecos electronic communication services gmbh
Internetconnect * Webserver/-design/-datenbanken * Consulting
Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz
E-Mail: [EMAIL PROTECTED] Voice: +49 6133 925151
WWW: http://www.ecos.de Fax: +49 6133 925152
-------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
