Hi,

    the thing is if I start mysql as root with '--user mysql' I get the 
'cannot create new
thread' thing which is why you put the CAP_SCHED_MGT thing in the manual I 
suppose.

But if I do an 'su' it works just alright without any need of this 
privilege, and it is only in
this context that all the tests pass.

I have tested this on three SGI servers and it is always the same: lock 
(wait on cond) at
some point or another when root and no problems when non-root.

I'm now testing our IMP (webmail) installation with mysql as non-root 
(started with su) to
see if the locking problem we have is gone (see my other posts in november 
and december).

I'll post confirmation if it works.

As for the select test, my machine has only 128 Mb so it could be in the 
range.  The
bizarre thing is I've tried it on bigger ones and it took more time (like 
400 or 500 s) :-)!

Thanks.
At 11:39 01-02-09 -0700, Sasha Pachev wrote:
>On Friday 09 February 2001 09:19, Robert Marchand wrote:
> >Hi,
> >
> >    this is a follow up to my problem with the test suite on an SGI O2 with
> >Irix 6.5.8f
> >
> >I manage to pass through all the tests without problems but a very long
> >'select' test:
> >
> >select          0,209           0,336           239,115         [pass]
> >
> >but thats another problem. The previous problem I had (hanging in 'delayed'
> >test) seems
>
>Select test is supposed to take a while - on PIII 500 with 256 MB RAM running
>Linux it takes 26 seconds. If your CPU is not that beefy you do not have very
>much RAM and the disks are slow, 239 seconds is to be expected.
>
> >du to the CAP_SCHED_MGT privilege as required by the doc.
> >
> >Let me explain:
> >
> >IF I run the tests with root OR with the CAP privilege attached to the
> >mysqld process, the
> >bug appears as said earlier.
> >
> >IF I run the tests with a user without this privilege, the tests are
> >fine.  When doing this,
> >threads appears to be OK.
> >
> >I'll now try if this privilege is really required on an Apache-mysql 
> context.
>
>That looks like some thread library bug. I would expect it to be the other
>way around, though. The privilege is required to create global scope threads
>- you should get errors if you do not have it. However, to be able to see
>what is up with this, we need to be able to log in to your machine.
>
>
>--
>MySQL Development Team
>    __  ___     ___ ____  __
>   /  |/  /_ __/ __/ __ \/ /   Sasha Pachev <[EMAIL PROTECTED]>
>  / /|_/ / // /\ \/ /_/ / /__  MySQL AB, http://www.mysql.com/
>/_/  /_/\_, /___/\___\_\___/  Provo, Utah, USA
>        <___/

-------
Robert Marchand                 tél: 343-6111 poste 5210
DGTIC-SIT                       e-mail: [EMAIL PROTECTED]
Université de Montréal          Montréal, Canada


---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Reply via email to