Re: Further FreeBSD 4.3 Issues (CPU hogging)

[Ken Menzel]

Hi Michael,
   Sorry for the delay getting back to you,  we had some network
problems here and are in the process of upgrading our 30 year old
copper to a new 200 pair copper cable to the building (They can't do
fiber, sigh!).  Anyway,  the output from truss that you sent looked
like a normal mysqld startup.  The way to run truss for debugging a
probelm is:
ps -ax | grep /mysqld
get the process ID and then truss -p process ID.
or as one command:
truss -p `ps -ax | grep /mysqld | cut -c 1-6`

Or are you saying this is what you did and there was no output at all
from truss?  IE it was "dead"?

P.S.  I will be out of the office tomorrow.
Ken
----- Original Message -----
From: "Institute For Social Ecology" <ise@stripped>
To: "Ken Menzel" <kenm@stripped>; <ise@stripped>;
<mysql@stripped>
Sent: Wednesday, August 01, 2001 4:56 PM
Subject: RE: Further FreeBSD 4.3 Issues (CPU hogging)


> Ken,
>
> Thanks as always for your very helpful support.  I did a 'truss -p'
on
> the PID and it came back empty handed.  I did do a 'truss
> /usr/local/libexec/mysqld' which spat back all sorts of goodies.  I
> have included the output bellow.  Also, as requested, below is the
> output of mysqlbug.
>
> Once again, thank you for your help.
>
> Regards,
>
> Michael
>
> truss /usr/local/libexec/mysqld:
>
> __sysctl(0xbfbffac4,0x2,0x281bfba8,0xbfbffac0,0x0,0x0) = 0 (0x0)
> mmap(0x0,32768,0x3,0x1002,-1,0x0)                = 672927744
> (0x281c1000)
> geteuid()                                        = 1048 (0x418)
> getuid()                                         = 1048 (0x418)
> getegid()                                        = 1048 (0x418)
> getgid()                                         = 1048 (0x418)
> open("/var/run/ld-elf.so.hints",0,00)            = 3 (0x3)
> read(0x3,0xbfbffaa4,0x80)                        = 128 (0x80)
> lseek(3,0x80,0)                                  = 128 (0x80)