From jw137282@sac.sfbay.sun.com Thu Jun 11 20:57:44 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n5C3vhUK022219 for ; Thu, 11 Jun 2009 20:57:44 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n5C3vfVB016351; Fri, 12 Jun 2009 11:57:42 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KL300I0PXO5CY00@nwk-avmta-2.sfbay.sun.com>; Thu, 11 Jun 2009 20:57:41 -0700 (PDT) Received: from dm-sfbay-01.sfbay.sun.com ([129.145.155.118]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KL300L0IXNXIGF0@nwk-avmta-2.sfbay.sun.com>; Thu, 11 Jun 2009 20:57:33 -0700 (PDT) Received: from sac.sfbay.sun.com (sac.SFBay.Sun.COM [129.146.226.132]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n5C3vXpc022676; Thu, 11 Jun 2009 20:57:33 -0700 (PDT) Received: from sac.sfbay.sun.com (localhost [127.0.0.1]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n5C3vWNh022214; Thu, 11 Jun 2009 20:57:32 -0700 (PDT) Received: (from jw137282@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id n5C3vWRZ022210; Thu, 11 Jun 2009 20:57:32 -0700 (PDT) Date: Thu, 11 Jun 2009 20:57:32 -0700 (PDT) From: James Walker Subject: sysbench [PSARC/2009/351 FastTrack timeout 06/18/2009] To: PSARC-ext@sun.com Cc: peter.rival@sun.com Message-id: <200906120357.n5C3vWRZ022210@sac.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 13217 I'm sponsoring this familiarity case for Peter Rival. The requested release binding is minor. The man page has been posted in the materials directory. Tim Cook of PAE has accepted this benchmark for inclusion in Solaris and a pointer to filebench has been added to the man page. Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: sysbench 1.2. Name of Document Author/Supplier: Author: Peter Rival 1.3 Date of This Document: 11 June, 2009 4. Technical Description Template Version: @(#)sac_nextcase %I% %G% SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: sysbench 1.2. Name of Document Author/Supplier: Author: Frank Rival 1.3 Date of This Document: 04 May, 2009 4. Technical Description Sysbench Check List 1.0 Project Information 1.1 Name of project/component sysbench 1.2 Author of document Frank.Rival@Sun.COM 2.0 Project Summary 2.1 Project Description SysBench is a modular, cross-platform and multi-threaded benchmark tool for evaluating OS parameters that are important for a system running a database under intensive load. The idea of this benchmark suite is to quickly get an impression about system performance without setting up complex database benchmarks or even without installing a database at all. Current features allow to test the following system parameters: * file I/O performance * scheduler performance * memory allocation and transfer speed * POSIX threads implementation performance * database server performance (OLTP benchmark) 2.2 Release binding What is is the release binding? (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/) [ ] Major [*] Minor [ ] Patch or Micro [ ] Unknown -- ARC review required 2.3 Type of project Is this case a Linux Familiarity project? [ ] Yes [*] No 2.4 Originating Community 2.4.1 Community Name Sysbench[1] 2.4.2 Community Involvement Indicate Sun's involvement in the community [ ] Maintainer [ ] Contributor [*] Monitoring Will the project team work with the upstream community to resolve architectural issues of interest to Sun? [*] Yes [ ] No - briefly explain Will we or are we forking from the community? [ ] Yes - ARC review required prior to forking [*] No 3.0 Technical Description 3.1 Installation & Sharable 3.1.1S Solaris Installation - section only required for Solaris Software (see http://opensolaris.org/os/community/arc/policies/install-locations/ for details) Does this project follow the Install Locations best practice? [*] Yes [ ] No - ARC review required Does this project install into /usr under [sbin|bin|lib|include|man|share]? [ ] Yes [*] No or N/A /usr/benchmarks/ - standard benchmark directory Does this project install into /opt? [ ] Yes - explain below [*] No or N/A Does this project install into a different directory structure? [*] Yes - ARC review required [ ] No or N/A Do any of the components of this project conflict with anything under /usr? (see http://opensolaris.org/os/community/arc/caselog/2007/047/ for details) [ ] Yes - explain below [*] No If conflicts exist then will this project install under /usr/gnu? [ ] Yes [ ] No - ARC review required [*] N/A Is this project installing into /usr/sfw? [ ] Yes - ARC review required [*] No 3.1.1W Windows Installation - section only required for Windows Software (see http://sac.sfbay/WSARC/2002/494 for details) Does this project install software into a :\Program Files\Sun\ or :\Sun\ directory? [ ] Yes [ ] No - ARC review required Does the project use the Windows registry? [ ] Yes [ ] No - ARC review required Does the project use HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\ for the registry key? [ ] Yes [ ] No - ARC review required Is the project's stored location HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\\Path? [ ] Yes [ ] No - ARC review required 3.1.2 Share and Sharable Does the module include any components that are used or shared by other projects? [ ] Yes [*] No If yes are these components packaged to be shared with the other FOSS? [ ] Yes [ ] No - ARC review required [*] N/A Are these components already in the Solaris WOS? [ ] Yes [*] No - continue with next section (section 3.2) If yes are these newer versions being delivered? [ ] Yes [ ] No - ARC review required If yes are the newer versions replacing the existing versions? [ ] Yes [ ] No - ARC review required 3.2 Exported Libraries Are libraries being delivered by this project? [ ] Yes [*] No - continue with next section (section 3.3) Are 64-bit versions of the libraries being delivered? [ ] Yes [ ] No - ARC review required Are static versions of the libraries being delivered? [ ] Yes - ARC review required [ ] No 3.3 Services and the /etc Directory (see http://opensolaris.org/os/community/arc/policies/SMF-policy/) Does the project integrate anything into /etc/init.d or /etc/rc?.d? [ ] Yes - ARC review required [*] No Does the project integrate any new entries into /etc/inittab or /etc/inetd.conf? [ ] Yes - ARC review required [*] No Does the project integrate any private non-public files into /etc/default or /etc/ configuration files? [ ] Yes - ARC review required [*] No Does the service manifests method context grant rights above that of the noaccess user and basic privilege set? [ ] Yes - ARC review required [*] No 3.4 Security 3.4.1 Secure By Default (see http://opensolaris.org/os/community/arc/policies/secure-by-default/ for details) (see http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for details) (see parts of http://opensolaris.org/os/community/arc/policies/SMF-policy/ for addtional details) Are there any network services provided by this project? [ ] Yes [*] No - continue with the next section (section 3.4.2) Are network services enabled by default? [ ] Yes - ARC review required [ ] No [ ] N/A Are network services automatically enabled by the project during installation? [ ] Yes - ARC review required [ ] No [ ] N/A Are inbound network communications denied by default? [ ] Yes [ ] No - ARC review required [ ] N/A Is inbound data checked to prevent content-based attacks? [ ] Yes [ ] No - ARC review required [ ] N/A Is the outbound receiver authenticated? [ ] Yes [ ] No - ARC review required [ ] N/A Is the receiver authenticated prior to receiving any sensitive outbound communication? [ ] Yes [ ] No - ARC review required [ ] N/A 3.4.2 Authorization (see http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ for details) Are there any setuid/setgid privileged binaries in the project? [ ] Yes - ARC review required [*] No - continue with next section (section 3.4.3) If yes then are the setuid/setgid privileges handled by the use of roles? [ ] Yes [ ] No - ARC review required 3.4.3 Auditing (see http://opensolaris.org/os/community/arc/policies/audit-policy/ for details) (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details) Does this component contain administrative or security enforcing software? [ ] Yes - ARC review required [*] No - continue to next section (section 3.4.4) (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details) Do the components create audit logs detailing what took place including what event took place, who was involved, when the event took place? [ ] Yes - ARC contract and Audit project team review required [*] No - ARC review required 3.4.4 Authentication (see http://opensolaris.org/os/community/arc/policies/PAM/) Do the components contain any authentication code? [ ] Yes [*] No - continue to next section (section 3.4.5) If yes do the components use PAM (plugable authentication modules) for authentication? [ ] Yes [ ] No - ARC review required If yes is a single PAM session maintained during authentication? [ ] Yes [ ] No - ARC review required If yes are the components sufficiently privileged to allow the requested operations (authentication, password change, process credential manipulation, audit state initialization)? [ ] Yes - briefly describe below [ ] No - ARC review required 3.4.5 Passwords (see http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ for details) Do any of the components for the project deal with passwords? [ ] Yes [*] No - continue to next section (section 3.4.6) If yes are these passwords entered via the CLI or environment? [ ] Yes - ARC review required [ ] No Are passwords stored within the file system for the component? [ ] Yes [ ] No - continue to next section (section 3.4.6) If yes are the permissions on the file such to protect exposing the password(s)? [ ] Yes [ ] No - ARC review required 3.4.6 General Security Questions (see http://opensolaris.org/os/community/arc/bestpractices/security-questions/ for details) Are there any network protocols used by this project? [*] Yes [ ] No - continue with the next section (section 3.5) Do the components use standard network protocols? [*] Yes [ ] No - ARC review required Do network services for the project make decisions based upon user, host or service identities? [ ] Yes - explain below [*] No [ ] N/A Do the components make use of secret information during authentication and/or authorization? [ ] Yes - explain below [*] No [ ] N/A 3.5 Networking Do the components access the network? [*] Yes [ ] No - continue with the next section (section 3.6) Sockets are used during database access. If yes do the components support IPv6? [ ] Yes [*] No - ARC review required 3.6 Core Solaris Components Do the components of this project compete with or duplicate core Solaris components? [ ] Yes - ARC review required [*] No Examples of Core Solaris Components include but are not limited to: Secure By Default Authorizations PAM -- Plugable Authentication Module Privilege PRM -- Process Rights Management -- Privilege Audit xVm -- Virtualization zones / Solaris Containers PRM -- Process Rights Management RBAC -- Role Based Access Control TX / Trusted Extensions ZFS SMF -- Service Management Facility FMA -- Fault Management Architecture SCF -- Smart Card Facility IPsec 4.0 Interfaces 4.1 Exported Interfaces Interface Name Classification Comments ---------------- ------------------- --------------------------- SUNWsysbench Uncommitted Package /usr/benchmarks/sysbench/sysbench Uncommitted Executable binary file 4.2 Imported Interfaces Interface Name Classification Comments --------------- -------------------- -------------------------- SUNWlibmsr Committed Math Package SUNWmysql5u Committed MySQL DBMS Appendix A - References [1] http://sysbench.sourceforge.net/ OSR ID# 10627 RFE ID# 6791652 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: SFW 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open From storycrafter@gmail.com Mon Jun 15 12:45:48 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n5FJjlpY029900 for ; Mon, 15 Jun 2009 12:45:47 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n5FJjetC004522; Mon, 15 Jun 2009 20:45:46 +0100 (BST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KLA0040XPKA2H00@brm-avmta-1.central.sun.com>; Mon, 15 Jun 2009 13:45:46 -0600 (MDT) Received: from sca-ea-mail-1.sun.com ([192.18.43.24]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KLA001BWPK90B10@brm-avmta-1.central.sun.com>; Mon, 15 Jun 2009 13:45:45 -0600 (MDT) Received: from relay14i.sun.com (ip124.net129179-4.block1.us.syntegra.com [129.179.4.124]) by sca-ea-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n5FJgKBn027911; Mon, 15 Jun 2009 19:45:45 +0000 (GMT) Received: from mmp13es.mmp.us.syntegra.com ([160.41.208.13] [160.41.208.13]) by relay14i.sun.com with ESMTP id BT-MMP-3197284; Mon, 15 Jun 2009 19:45:44 +0000 (Z) Received: from relay14i.sun.com (relay14i.sun.com [129.179.4.124]) by mmp13es.mmp.us.syntegra.com with ESMTP id BT-MMP-112671631; Mon, 15 Jun 2009 19:45:26 +0000 (Z) Received: from mail-px0-f198.google.com ([209.85.216.198] [209.85.216.198]) by relay1i.sun.com with ESMTP id BT-MMP-14649547; Mon, 15 Jun 2009 19:45:26 +0000 (Z) Received: by pxi36 with SMTP id 36so3658374pxi.30 for ; Mon, 15 Jun 2009 12:45:24 -0700 (PDT) Received: by 10.114.149.2 with SMTP id w2mr12119065wad.182.1245095124655; Mon, 15 Jun 2009 12:45:24 -0700 (PDT) Received: from ?172.16.202.89? (68-252-106-20.ded.ameritech.net [68.252.106.20]) by mx.google.com with ESMTPS id m34sm6836019waf.56.2009.06.15.12.45.22 (version=TLSv1/SSLv3 cipher=RC4-MD5) ; Mon, 15 Jun 2009 12:45:23 -0700 (PDT) Date: Mon, 15 Jun 2009 14:45:21 -0500 From: Mark Martin Subject: Re: sysbench [PSARC/2009/351 FastTrack timeout 06/18/2009] In-reply-to: <200906120357.n5C3vWRZ022210@sac.sfbay.sun.com> To: peter.rival@sun.com Cc: James Walker , PSARC-ext@sun.com Message-id: <4A36A4D1.20600@gmail.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=u6bwNTseHt+ccz3G+vQALhS+3jzREDmcirDiWV02aaM=; b=TocUf/B74RyPDtws6XaagnuIH2J1akCn3Ou43+CKiNYeLCScjMFS7Xai9L42jfaEw/ X8kjCZbB00MsjqX8ASVTuB1X0RUM+3GX/EDEAgNty/UW7K7THqWQp+wnikl87icRtlhq D2+5Fh4S6spV9FYSQ9d8rE0xl0lkbg5apSOmk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=yA8VvS3SXxxCKe2woqH7VU9dwvrAJ02Kk4pyiiXybXreLF2DK2eF9NeH03/mHOLdzA 0lPU0B8lrwe9sb/ZmAHXVUYY9TwjjIdcfFgg3Y/JNLLjD8jicq7FgInWNXNUy2rLurT4 FG6ZoMggV+FlQSJebOeABcI/wdyfvt8nwmvvQ= X-PMX-Version: 5.4.1.325704 X-Brightmail-Tracker: AAAAAA== X-Antispam: No, score=-2.6/5.0, scanned in 6.056sec at (localhost [127.0.0.1]) by smf-spamd v1.3.1 - http://smfs.sf.net/ References: <200906120357.n5C3vWRZ022210@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) Status: RO Content-Length: 14589 James Walker wrote: > I'm sponsoring this familiarity case for Peter Rival. The requested > release binding is minor. The man page has been posted in the > materials directory. Tim Cook of PAE has accepted this benchmark > for inclusion in Solaris and a pointer to filebench has been added > to the man page. > Minor nit -- you mention it's a "familiarity case", which seems reasonable, yet 2.3 says "no". Other comments inline below. > Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI > This information is Copyright 2009 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > sysbench > 1.2. Name of Document Author/Supplier: > Author: Peter Rival > 1.3 Date of This Document: > 11 June, 2009 > 4. Technical Description > Template Version: @(#)sac_nextcase %I% %G% SMI > This information is Copyright 2009 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > sysbench > 1.2. Name of Document Author/Supplier: > Author: Frank Rival > 1.3 Date of This Document: > 04 May, 2009 > 4. Technical Description > Sysbench Check List > 1.0 Project Information > 1.1 Name of project/component > sysbench > > 1.2 Author of document > Frank.Rival@Sun.COM > > 2.0 Project Summary > 2.1 Project Description > SysBench is a modular, cross-platform and multi-threaded benchmark tool > for evaluating OS parameters that are important for a system running a > database under intensive load. > > The idea of this benchmark suite is to quickly get an impression about > system performance without setting up complex database benchmarks or > even without installing a database at all. > Current features allow to test the following system parameters: > > * file I/O performance > * scheduler performance > * memory allocation and transfer speed > * POSIX threads implementation performance > * database server performance (OLTP benchmark) > > > 2.2 Release binding > What is is the release binding? > (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/) > [ ] Major > [*] Minor > [ ] Patch or Micro > [ ] Unknown -- ARC review required > > 2.3 Type of project > Is this case a Linux Familiarity project? > [ ] Yes > [*] No > > 2.4 Originating Community > 2.4.1 Community Name > Sysbench[1] > > 2.4.2 Community Involvement > Indicate Sun's involvement in the community > [ ] Maintainer > [ ] Contributor > [*] Monitoring > > Will the project team work with the upstream community to resolve > architectural issues of interest to Sun? > [*] Yes > [ ] No - briefly explain > > Will we or are we forking from the community? > [ ] Yes - ARC review required prior to forking > [*] No > > 3.0 Technical Description > 3.1 Installation & Sharable > 3.1.1S Solaris Installation - section only required for Solaris Software > (see http://opensolaris.org/os/community/arc/policies/install-locations/ for details) > Does this project follow the Install Locations best practice? > [*] Yes > [ ] No - ARC review required > > Does this project install into /usr under [sbin|bin|lib|include|man|share]? > [ ] Yes > [*] No or N/A > > /usr/benchmarks/ - standard benchmark directory > > Does this project install into /opt? > [ ] Yes - explain below > [*] No or N/A > > Does this project install into a different directory structure? > [*] Yes - ARC review required > [ ] No or N/A > > Do any of the components of this project conflict with anything under /usr? > (see http://opensolaris.org/os/community/arc/caselog/2007/047/ for details) > [ ] Yes - explain below > [*] No > > If conflicts exist then will this project install under /usr/gnu? > [ ] Yes > [ ] No - ARC review required > [*] N/A > > Is this project installing into /usr/sfw? > [ ] Yes - ARC review required > [*] No > > 3.1.1W Windows Installation - section only required for Windows Software > (see http://sac.sfbay/WSARC/2002/494 for details) > Does this project install software into a > :\Program Files\Sun\ or :\Sun\ > directory? > [ ] Yes > [ ] No - ARC review required > > Does the project use the Windows registry? > [ ] Yes > [ ] No - ARC review required > > Does the project use > HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\ > for the registry key? > [ ] Yes > [ ] No - ARC review required > > Is the project's stored location > HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\\Path? > [ ] Yes > [ ] No - ARC review required > > 3.1.2 Share and Sharable > Does the module include any components that are used or shared by > other projects? > [ ] Yes > [*] No > > If yes are these components packaged to be shared with the other FOSS? > [ ] Yes > [ ] No - ARC review required > [*] N/A > > Are these components already in the Solaris WOS? > [ ] Yes > [*] No - continue with next section (section 3.2) > > If yes are these newer versions being delivered? > [ ] Yes > [ ] No - ARC review required > > If yes are the newer versions replacing the existing versions? > [ ] Yes > [ ] No - ARC review required > > 3.2 Exported Libraries > Are libraries being delivered by this project? > [ ] Yes > [*] No - continue with next section (section 3.3) > > Are 64-bit versions of the libraries being delivered? > [ ] Yes > [ ] No - ARC review required > > Are static versions of the libraries being delivered? > [ ] Yes - ARC review required > [ ] No > > 3.3 Services and the /etc Directory > (see http://opensolaris.org/os/community/arc/policies/SMF-policy/) > Does the project integrate anything into /etc/init.d or /etc/rc?.d? > [ ] Yes - ARC review required > [*] No > > Does the project integrate any new entries into /etc/inittab or > /etc/inetd.conf? > [ ] Yes - ARC review required > [*] No > > Does the project integrate any private non-public files into /etc/default > or /etc/ configuration files? > [ ] Yes - ARC review required > [*] No > > Does the service manifests method context grant rights above that > of the noaccess user and basic privilege set? > [ ] Yes - ARC review required > [*] No > > 3.4 Security > 3.4.1 Secure By Default > (see http://opensolaris.org/os/community/arc/policies/secure-by-default/ for details) > (see http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for details) > (see parts of http://opensolaris.org/os/community/arc/policies/SMF-policy/ for > addtional details) > Are there any network services provided by this project? > [ ] Yes > [*] No - continue with the next section (section 3.4.2) > > Are network services enabled by default? > [ ] Yes - ARC review required > [ ] No > [ ] N/A > > Are network services automatically enabled by the project during installation? > [ ] Yes - ARC review required > [ ] No > [ ] N/A > > Are inbound network communications denied by default? > [ ] Yes > [ ] No - ARC review required > [ ] N/A > > Is inbound data checked to prevent content-based attacks? > [ ] Yes > [ ] No - ARC review required > [ ] N/A > > Is the outbound receiver authenticated? > [ ] Yes > [ ] No - ARC review required > [ ] N/A > > Is the receiver authenticated prior to receiving any sensitive outbound communication? > [ ] Yes > [ ] No - ARC review required > [ ] N/A > > 3.4.2 Authorization > (see http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and > http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and > http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ > for details) > Are there any setuid/setgid privileged binaries in the project? > [ ] Yes - ARC review required > [*] No - continue with next section (section 3.4.3) > > If yes then are the setuid/setgid privileges handled by the use of roles? > [ ] Yes > [ ] No - ARC review required > > 3.4.3 Auditing > (see http://opensolaris.org/os/community/arc/policies/audit-policy/ for details) > (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details) > Does this component contain administrative or security enforcing software? > [ ] Yes - ARC review required > [*] No - continue to next section (section 3.4.4) > > (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details) > Do the components create audit logs detailing what took place including what event > took place, who was involved, when the event took place? > [ ] Yes - ARC contract and Audit project team review required > [*] No - ARC review required > > > 3.4.4 Authentication > (see http://opensolaris.org/os/community/arc/policies/PAM/) > Do the components contain any authentication code? > [ ] Yes > [*] No - continue to next section (section 3.4.5) > > If yes do the components use PAM (plugable authentication modules) for authentication? > [ ] Yes > [ ] No - ARC review required > > If yes is a single PAM session maintained during authentication? > [ ] Yes > [ ] No - ARC review required > > If yes are the components sufficiently privileged to allow the requested > operations (authentication, password change, process credential manipulation, > audit state initialization)? > [ ] Yes - briefly describe below > [ ] No - ARC review required > > 3.4.5 Passwords > (see http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and > http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ for details) > Do any of the components for the project deal with passwords? > [ ] Yes > [*] No - continue to next section (section 3.4.6) > The mysql driver support isn't included? This is in conflict with your clarification on question 3.5 isn't it? If it is included, is it important to note that the user/pass are specified on the command line? > > If yes are these passwords entered via the CLI or environment? > [ ] Yes - ARC review required > [ ] No > > Are passwords stored within the file system for the component? > [ ] Yes > [ ] No - continue to next section (section 3.4.6) > > If yes are the permissions on the file such to protect exposing the password(s)? > [ ] Yes > [ ] No - ARC review required > > 3.4.6 General Security Questions > (see http://opensolaris.org/os/community/arc/bestpractices/security-questions/ for details) > Are there any network protocols used by this project? > [*] Yes > [ ] No - continue with the next section (section 3.5) > > Do the components use standard network protocols? > [*] Yes > [ ] No - ARC review required > > Do network services for the project make decisions based upon user, host or > service identities? > [ ] Yes - explain below > [*] No > [ ] N/A > > Do the components make use of secret information during authentication and/or > authorization? > [ ] Yes - explain below > [*] No > [ ] N/A > > 3.5 Networking > Do the components access the network? > [*] Yes > [ ] No - continue with the next section (section 3.6) > > Sockets are used during database access. > > > If yes do the components support IPv6? > [ ] Yes > [*] No - ARC review required > > 3.6 Core Solaris Components > Do the components of this project compete with or duplicate core > Solaris components? > [ ] Yes - ARC review required > [*] No > > Examples of Core Solaris Components include but are not limited to: > > Secure By Default > Authorizations > PAM -- Plugable Authentication Module > Privilege > PRM -- Process Rights Management -- Privilege > Audit > xVm -- Virtualization > zones / Solaris Containers > PRM -- Process Rights Management > RBAC -- Role Based Access Control > TX / Trusted Extensions > ZFS > SMF -- Service Management Facility > FMA -- Fault Management Architecture > SCF -- Smart Card Facility > IPsec > > 4.0 Interfaces > 4.1 Exported Interfaces > > Interface Name Classification Comments > ---------------- ------------------- --------------------------- > SUNWsysbench Uncommitted Package > > /usr/benchmarks/sysbench/sysbench > Uncommitted Executable binary file > PSARC 2007/448 set the precedent that this should probably be /usr/benchmarks/sysbench/bin/sysbench > > 4.2 Imported Interfaces > > Interface Name Classification Comments > --------------- -------------------- -------------------------- > SUNWlibmsr Committed Math Package > SUNWmysql5u Committed MySQL DBMS > > Appendix A - References > [1] http://sysbench.sourceforge.net/ > > OSR ID# 10627 > RFE ID# 6791652 > > > 6. Resources and Schedule > 6.4. Steering Committee requested information > 6.4.1. Consolidation C-team Name: > SFW > 6.5. ARC review type: FastTrack > 6.6. ARC Exposure: open > > _______________________________________________ > opensolaris-arc mailing list > opensolaris-arc@opensolaris.org > From Kais.Belgaied@sun.com Mon Jun 15 15:51:49 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n5FMpn2g007146 for ; Mon, 15 Jun 2009 15:51:49 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n5FMpl2A016256; Mon, 15 Jun 2009 23:51:48 +0100 (BST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KLA00903Y6A3P00@nwk-avmta-2.sfbay.sun.com>; Mon, 15 Jun 2009 15:51:46 -0700 (PDT) Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.59]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KLA00H8XY69HPC0@nwk-avmta-2.sfbay.sun.com>; Mon, 15 Jun 2009 15:51:45 -0700 (PDT) Received: from [129.146.11.146] (sr1-jurassic-03.SFBay.Sun.COM [129.146.11.146]) by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n5FMpinY644820; Mon, 15 Jun 2009 15:51:45 -0700 (PDT) Date: Mon, 15 Jun 2009 15:51:44 -0700 From: Kais Belgaied Subject: Re: sysbench [PSARC/2009/351 FastTrack timeout 06/18/2009] In-reply-to: <200906120357.n5C3vWRZ022210@sac.sfbay.sun.com> To: James Walker Cc: PSARC-ext@sun.com, peter.rival@sun.com Reply-to: Kais.Belgaied@sun.com Message-id: <4A36D080.8020205@Sun.COM> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200906120357.n5C3vWRZ022210@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.19 (X11/20090110) Status: RO Content-Length: 14240 +1 , a quick question though: the release binding is minor, is there a dependency on future minor release features that are not available yet as patches to the current minor release of Solaris? Kais On 06/11/09 20:57, James Walker wrote: > I'm sponsoring this familiarity case for Peter Rival. The requested > release binding is minor. The man page has been posted in the > materials directory. Tim Cook of PAE has accepted this benchmark > for inclusion in Solaris and a pointer to filebench has been added > to the man page. > > Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI > This information is Copyright 2009 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > sysbench > 1.2. Name of Document Author/Supplier: > Author: Peter Rival > 1.3 Date of This Document: > 11 June, 2009 > 4. Technical Description > Template Version: @(#)sac_nextcase %I% %G% SMI > This information is Copyright 2009 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > sysbench > 1.2. Name of Document Author/Supplier: > Author: Frank Rival > 1.3 Date of This Document: > 04 May, 2009 > 4. Technical Description > Sysbench Check List > 1.0 Project Information > 1.1 Name of project/component > sysbench > > 1.2 Author of document > Frank.Rival@Sun.COM > > 2.0 Project Summary > 2.1 Project Description > SysBench is a modular, cross-platform and multi-threaded benchmark tool > for evaluating OS parameters that are important for a system running a > database under intensive load. > > The idea of this benchmark suite is to quickly get an impression about > system performance without setting up complex database benchmarks or > even without installing a database at all. > Current features allow to test the following system parameters: > > * file I/O performance > * scheduler performance > * memory allocation and transfer speed > * POSIX threads implementation performance > * database server performance (OLTP benchmark) > > > 2.2 Release binding > What is is the release binding? > (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/) > [ ] Major > [*] Minor > [ ] Patch or Micro > [ ] Unknown -- ARC review required > > 2.3 Type of project > Is this case a Linux Familiarity project? > [ ] Yes > [*] No > > 2.4 Originating Community > 2.4.1 Community Name > Sysbench[1] > > 2.4.2 Community Involvement > Indicate Sun's involvement in the community > [ ] Maintainer > [ ] Contributor > [*] Monitoring > > Will the project team work with the upstream community to resolve > architectural issues of interest to Sun? > [*] Yes > [ ] No - briefly explain > > Will we or are we forking from the community? > [ ] Yes - ARC review required prior to forking > [*] No > > 3.0 Technical Description > 3.1 Installation & Sharable > 3.1.1S Solaris Installation - section only required for Solaris Software > (see http://opensolaris.org/os/community/arc/policies/install-locations/ for details) > Does this project follow the Install Locations best practice? > [*] Yes > [ ] No - ARC review required > > Does this project install into /usr under [sbin|bin|lib|include|man|share]? > [ ] Yes > [*] No or N/A > > /usr/benchmarks/ - standard benchmark directory > > Does this project install into /opt? > [ ] Yes - explain below > [*] No or N/A > > Does this project install into a different directory structure? > [*] Yes - ARC review required > [ ] No or N/A > > Do any of the components of this project conflict with anything under /usr? > (see http://opensolaris.org/os/community/arc/caselog/2007/047/ for details) > [ ] Yes - explain below > [*] No > > If conflicts exist then will this project install under /usr/gnu? > [ ] Yes > [ ] No - ARC review required > [*] N/A > > Is this project installing into /usr/sfw? > [ ] Yes - ARC review required > [*] No > > 3.1.1W Windows Installation - section only required for Windows Software > (see http://sac.sfbay/WSARC/2002/494 for details) > Does this project install software into a > :\Program Files\Sun\ or :\Sun\ > directory? > [ ] Yes > [ ] No - ARC review required > > Does the project use the Windows registry? > [ ] Yes > [ ] No - ARC review required > > Does the project use > HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\ > for the registry key? > [ ] Yes > [ ] No - ARC review required > > Is the project's stored location > HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\\Path? > [ ] Yes > [ ] No - ARC review required > > 3.1.2 Share and Sharable > Does the module include any components that are used or shared by > other projects? > [ ] Yes > [*] No > > If yes are these components packaged to be shared with the other FOSS? > [ ] Yes > [ ] No - ARC review required > [*] N/A > > Are these components already in the Solaris WOS? > [ ] Yes > [*] No - continue with next section (section 3.2) > > If yes are these newer versions being delivered? > [ ] Yes > [ ] No - ARC review required > > If yes are the newer versions replacing the existing versions? > [ ] Yes > [ ] No - ARC review required > > 3.2 Exported Libraries > Are libraries being delivered by this project? > [ ] Yes > [*] No - continue with next section (section 3.3) > > Are 64-bit versions of the libraries being delivered? > [ ] Yes > [ ] No - ARC review required > > Are static versions of the libraries being delivered? > [ ] Yes - ARC review required > [ ] No > > 3.3 Services and the /etc Directory > (see http://opensolaris.org/os/community/arc/policies/SMF-policy/) > Does the project integrate anything into /etc/init.d or /etc/rc?.d? > [ ] Yes - ARC review required > [*] No > > Does the project integrate any new entries into /etc/inittab or > /etc/inetd.conf? > [ ] Yes - ARC review required > [*] No > > Does the project integrate any private non-public files into /etc/default > or /etc/ configuration files? > [ ] Yes - ARC review required > [*] No > > Does the service manifests method context grant rights above that > of the noaccess user and basic privilege set? > [ ] Yes - ARC review required > [*] No > > 3.4 Security > 3.4.1 Secure By Default > (see http://opensolaris.org/os/community/arc/policies/secure-by-default/ for details) > (see http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for details) > (see parts of http://opensolaris.org/os/community/arc/policies/SMF-policy/ for > addtional details) > Are there any network services provided by this project? > [ ] Yes > [*] No - continue with the next section (section 3.4.2) > > Are network services enabled by default? > [ ] Yes - ARC review required > [ ] No > [ ] N/A > > Are network services automatically enabled by the project during installation? > [ ] Yes - ARC review required > [ ] No > [ ] N/A > > Are inbound network communications denied by default? > [ ] Yes > [ ] No - ARC review required > [ ] N/A > > Is inbound data checked to prevent content-based attacks? > [ ] Yes > [ ] No - ARC review required > [ ] N/A > > Is the outbound receiver authenticated? > [ ] Yes > [ ] No - ARC review required > [ ] N/A > > Is the receiver authenticated prior to receiving any sensitive outbound communication? > [ ] Yes > [ ] No - ARC review required > [ ] N/A > > 3.4.2 Authorization > (see http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and > http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and > http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ > for details) > Are there any setuid/setgid privileged binaries in the project? > [ ] Yes - ARC review required > [*] No - continue with next section (section 3.4.3) > > If yes then are the setuid/setgid privileges handled by the use of roles? > [ ] Yes > [ ] No - ARC review required > > 3.4.3 Auditing > (see http://opensolaris.org/os/community/arc/policies/audit-policy/ for details) > (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details) > Does this component contain administrative or security enforcing software? > [ ] Yes - ARC review required > [*] No - continue to next section (section 3.4.4) > > (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details) > Do the components create audit logs detailing what took place including what event > took place, who was involved, when the event took place? > [ ] Yes - ARC contract and Audit project team review required > [*] No - ARC review required > > > 3.4.4 Authentication > (see http://opensolaris.org/os/community/arc/policies/PAM/) > Do the components contain any authentication code? > [ ] Yes > [*] No - continue to next section (section 3.4.5) > > If yes do the components use PAM (plugable authentication modules) for authentication? > [ ] Yes > [ ] No - ARC review required > > If yes is a single PAM session maintained during authentication? > [ ] Yes > [ ] No - ARC review required > > If yes are the components sufficiently privileged to allow the requested > operations (authentication, password change, process credential manipulation, > audit state initialization)? > [ ] Yes - briefly describe below > [ ] No - ARC review required > > 3.4.5 Passwords > (see http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and > http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ for details) > Do any of the components for the project deal with passwords? > [ ] Yes > [*] No - continue to next section (section 3.4.6) > > If yes are these passwords entered via the CLI or environment? > [ ] Yes - ARC review required > [ ] No > > Are passwords stored within the file system for the component? > [ ] Yes > [ ] No - continue to next section (section 3.4.6) > > If yes are the permissions on the file such to protect exposing the password(s)? > [ ] Yes > [ ] No - ARC review required > > 3.4.6 General Security Questions > (see http://opensolaris.org/os/community/arc/bestpractices/security-questions/ for details) > Are there any network protocols used by this project? > [*] Yes > [ ] No - continue with the next section (section 3.5) > > Do the components use standard network protocols? > [*] Yes > [ ] No - ARC review required > > Do network services for the project make decisions based upon user, host or > service identities? > [ ] Yes - explain below > [*] No > [ ] N/A > > Do the components make use of secret information during authentication and/or > authorization? > [ ] Yes - explain below > [*] No > [ ] N/A > > 3.5 Networking > Do the components access the network? > [*] Yes > [ ] No - continue with the next section (section 3.6) > > Sockets are used during database access. > > If yes do the components support IPv6? > [ ] Yes > [*] No - ARC review required > > 3.6 Core Solaris Components > Do the components of this project compete with or duplicate core > Solaris components? > [ ] Yes - ARC review required > [*] No > > Examples of Core Solaris Components include but are not limited to: > > Secure By Default > Authorizations > PAM -- Plugable Authentication Module > Privilege > PRM -- Process Rights Management -- Privilege > Audit > xVm -- Virtualization > zones / Solaris Containers > PRM -- Process Rights Management > RBAC -- Role Based Access Control > TX / Trusted Extensions > ZFS > SMF -- Service Management Facility > FMA -- Fault Management Architecture > SCF -- Smart Card Facility > IPsec > > 4.0 Interfaces > 4.1 Exported Interfaces > > Interface Name Classification Comments > ---------------- ------------------- --------------------------- > SUNWsysbench Uncommitted Package > > /usr/benchmarks/sysbench/sysbench > Uncommitted Executable binary file > > 4.2 Imported Interfaces > > Interface Name Classification Comments > --------------- -------------------- -------------------------- > SUNWlibmsr Committed Math Package > SUNWmysql5u Committed MySQL DBMS > > Appendix A - References > [1] http://sysbench.sourceforge.net/ > > OSR ID# 10627 > RFE ID# 6791652 > > > 6. Resources and Schedule > 6.4. Steering Committee requested information > 6.4.1. Consolidation C-team Name: > SFW > 6.5. ARC review type: FastTrack > 6.6. ARC Exposure: open > > > From James.Walker@Sun.COM Wed Jun 17 08:46:34 2009 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n5HFkY1X012681 for ; Wed, 17 Jun 2009 08:46:34 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n5HFkXkR029773; Wed, 17 Jun 2009 09:46:33 -0600 (MDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KLE00F0D3TL5B00@brm-avmta-1.central.sun.com>; Wed, 17 Jun 2009 09:46:33 -0600 (MDT) Received: from brmea-mail-1.sun.com ([192.18.98.31]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KLE003UX3THCMD0@brm-avmta-1.central.sun.com>; Wed, 17 Jun 2009 09:46:29 -0600 (MDT) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n5HFkTFm021635; Wed, 17 Jun 2009 15:46:29 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KLE007003E5WI00@mail-amer.sun.com>; Wed, 17 Jun 2009 09:46:29 -0600 (MDT) Received: from c-67-166-22-238.hsd1.co.comcast.net ([unknown] [129.150.33.82]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KLE00DSR3T9WF50@mail-amer.sun.com>; Wed, 17 Jun 2009 09:46:21 -0600 (MDT) Date: Wed, 17 Jun 2009 09:46:21 -0600 From: Jim Walker Subject: Re: sysbench [PSARC/2009/351 FastTrack timeout 06/18/2009] In-reply-to: <4A36A4D1.20600@gmail.com> Sender: James.Walker@Sun.COM To: Mark Martin Cc: peter.rival@Sun.COM, PSARC-ext@Sun.COM Reply-to: James.Walker@Sun.COM Message-id: <4A390FCD.4060604@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200906120357.n5C3vWRZ022210@sac.sfbay.sun.com> <4A36A4D1.20600@gmail.com> User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302) Status: RO Content-Length: 146 Mark Martin wrote: > > Minor nit -- you mention it's a "familiarity case", which seems > reasonable, yet 2.3 says "no". > Fixed. Cheers, Jim From James.Walker@Sun.COM Wed Jun 17 09:57:14 2009 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n5HGvEVI016031 for ; Wed, 17 Jun 2009 09:57:14 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n5HGvEBu011706; Wed, 17 Jun 2009 09:57:14 -0700 (PDT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KLE00A1573EAY00@nwk-avmta-2.sfbay.sun.com>; Wed, 17 Jun 2009 09:57:14 -0700 (PDT) Received: from brmea-mail-1.sun.com ([192.18.98.31]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KLE002DF73DE1B0@nwk-avmta-2.sfbay.sun.com>; Wed, 17 Jun 2009 09:57:13 -0700 (PDT) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n5HGvCMQ029633; Wed, 17 Jun 2009 16:57:13 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KLE0050065YY600@mail-amer.sun.com>; Wed, 17 Jun 2009 10:57:12 -0600 (MDT) Received: from c-67-166-22-238.hsd1.co.comcast.net ([unknown] [129.150.33.82]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KLE00AB572SBF20@mail-amer.sun.com>; Wed, 17 Jun 2009 10:56:52 -0600 (MDT) Date: Wed, 17 Jun 2009 10:56:52 -0600 From: Jim Walker Subject: Re: sysbench [PSARC/2009/351 FastTrack timeout 06/18/2009] In-reply-to: <4A36D080.8020205@Sun.COM> Sender: James.Walker@Sun.COM To: Kais.Belgaied@Sun.COM Cc: psarc-ext@Sun.COM, peter.rival@Sun.COM Reply-to: James.Walker@Sun.COM Message-id: <4A392054.8000106@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200906120357.n5C3vWRZ022210@sac.sfbay.sun.com> <4A36D080.8020205@Sun.COM> User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302) Status: RO Content-Length: 299 Kais Belgaied wrote: > +1 , a quick question though: the release binding is minor, is there > a dependency on future minor release features that are not available > yet as patches to the current minor release of Solaris? No. But can you rephrase, since the question seems too general. Cheers, Jim From peter.rival@sun.com Wed Jun 17 20:07:05 2009 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n5I374Pl012972 for ; Wed, 17 Jun 2009 20:07:04 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n5I374PX008959 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 17 Jun 2009 21:07:04 -0600 (MDT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KLE00303ZBRZC00@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 17 Jun 2009 20:07:03 -0700 (PDT) Received: from brmea-mail-1.sun.com ([192.18.98.31]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KLE001BKZBOOH10@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 17 Jun 2009 20:07:01 -0700 (PDT) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n5I3708e025661 for ; Thu, 18 Jun 2009 03:07:00 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KLE00400Z4YWC00@mail-amer.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 17 Jun 2009 21:07:00 -0600 (MDT) Received: from [192.168.1.102] ([unknown] [76.118.173.225]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KLE00IJPZBNWK30@mail-amer.sun.com>; Wed, 17 Jun 2009 21:07:00 -0600 (MDT) Date: Wed, 17 Jun 2009 23:07:00 -0400 From: Peter Rival Subject: Re: sysbench [PSARC/2009/351 FastTrack timeout 06/18/2009] In-reply-to: <4A36A4D1.20600@gmail.com> Sender: Frank.Rival@sun.com To: Mark Martin Cc: James Walker , PSARC-ext@sun.com Message-id: <4A39AF54.3090807@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200906120357.n5C3vWRZ022210@sac.sfbay.sun.com> <4A36A4D1.20600@gmail.com> User-Agent: Thunderbird 2.0.0.21 (X11/20090323) Status: RO Content-Length: 1732 Thanks to Jim Walker for pointing me to the inlined comments - until now I'd missed them. My apologies. Mark Martin wrote: > James Walker wrote: >> >> 3.4.5 Passwords >> (see >> http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and >> >> http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ >> for details) >> Do any of the components for the project deal with passwords? >> [ ] Yes >> [*] No - continue to next section (section 3.4.6) >> > The mysql driver support isn't included? This is in conflict with > your clarification on question 3.5 isn't it? If it is included, is it > important to note that the user/pass are specified on the command line? The mysql driver uses a thin shim that uses libmysql to talk to the mysql database. You are correct that it does indeed deal with passwords and that they are specified on the command line. The general use I've seen is to use the default username and have no set password but that is not required. >> >> 4.0 Interfaces >> 4.1 Exported Interfaces >> Interface Name Classification Comments >> ---------------- ------------------- >> --------------------------- >> SUNWsysbench Uncommitted Package >> >> /usr/benchmarks/sysbench/sysbench >> Uncommitted Executable binary file >> > > PSARC 2007/448 set the precedent that this should probably be > /usr/benchmarks/sysbench/bin/sysbench > Understood, and I'll make the change. I had been distracted by PSARC 2008/461 (bonnie++) which did not use the bin directory. Should I also add a symlink in /usr/bin as in 2007/461? - Pete From storycrafter@gmail.com Thu Jun 18 09:14:46 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n5IGEkfU000045 for ; Thu, 18 Jun 2009 09:14:46 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n5IGEf83026861; Thu, 18 Jun 2009 17:14:45 +0100 (BST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KLF00705ZSIWJ00@nwk-avmta-2.sfbay.sun.com>; Thu, 18 Jun 2009 09:14:42 -0700 (PDT) Received: from sca-ea-mail-1.sun.com ([192.18.43.24]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KLF0042DZSHXI40@nwk-avmta-2.sfbay.sun.com>; Thu, 18 Jun 2009 09:14:41 -0700 (PDT) Received: from relay15i.sun.com (ip125.net129179-4.block1.us.syntegra.com [129.179.4.125]) by sca-ea-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n5IGEfal028054; Thu, 18 Jun 2009 16:14:41 +0000 (GMT) Received: from mmp11es.mmp.us.syntegra.com ([160.41.208.11] [160.41.208.11]) by relay15i.sun.com with ESMTP id BT-MMP-1021763; Thu, 18 Jun 2009 16:14:41 +0000 (Z) Received: from relay14i.sun.com (relay14i.sun.com [129.179.4.124]) by mmp11es.mmp.us.syntegra.com with ESMTP id BT-MMP-95865373; Thu, 18 Jun 2009 16:14:39 +0000 (Z) Received: from mail-ew0-f205.google.com ([209.85.219.205] [209.85.219.205]) by relay1i.sun.com with ESMTP id BT-MMP-22006076; Thu, 18 Jun 2009 16:14:38 +0000 (Z) Received: by ewy1 with SMTP id 1so1626332ewy.8 for ; Thu, 18 Jun 2009 09:13:40 -0700 (PDT) Received: by 10.210.12.18 with SMTP id 18mr2038999ebl.2.1245341620585; Thu, 18 Jun 2009 09:13:40 -0700 (PDT) Received: from ?172.16.202.89? (68-252-106-20.ded.ameritech.net [68.252.106.20]) by mx.google.com with ESMTPS id 10sm17223eyz.31.2009.06.18.09.13.38 (version=TLSv1/SSLv3 cipher=RC4-MD5) ; Thu, 18 Jun 2009 09:13:39 -0700 (PDT) Date: Thu, 18 Jun 2009 11:13:36 -0500 From: Mark Martin Subject: Re: sysbench [PSARC/2009/351 FastTrack timeout 06/18/2009] In-reply-to: <4A39AF54.3090807@sun.com> To: Peter Rival Cc: James Walker , psarc-ext@sun.com Message-id: <4A3A67B0.50608@gmail.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=EqPzPcqGQTVjYglSho83iprocYcC2iTuHjQpi7A6kVI=; b=XW8adximSvkPlpTCLE0EMhnBTgXnqlk2OAbKu6D50D+qByw9S51YeGiji8WuDnRkBW j6IEgEjNjsCmIjBhh4gTOCtoXccXZMhdYqrWcUt5vXkikW8aS4Vz08KGck1BnhrdLSMM kVn9v56KQEl8EEP3GqIhIp9KnytgCstXmBW9Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=PITtFy0dN6fD6ErDvXQTz3pwV9/hL6+O/MyLs2s87Rhcb78nn2stmMsxFFYiUl/R6H SY+8ql5ztPlWT4xPQX6K06LaiA1D5xAlb75cqjPvmkAIz0Afa2XetCE5PpAqQMOUbCKw pF4Ooz2NvsIs+8q/0xO6fqc0AXU2tW9mU4Z2s= X-PMX-Version: 5.4.1.325704 X-Brightmail-Tracker: AAAAAA== X-Antispam: No, score=-2.6/5.0, scanned in 2.044sec at (localhost [127.0.0.1]) by smf-spamd v1.3.1 - http://smfs.sf.net/ References: <200906120357.n5C3vWRZ022210@sac.sfbay.sun.com> <4A36A4D1.20600@gmail.com> <4A39AF54.3090807@sun.com> User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) Status: RO Content-Length: 2575 Peter Rival wrote: > Thanks to Jim Walker for pointing me to the inlined comments - until > now I'd missed them. My apologies. > No worries, I kinda wondered if I shouldn't have trimmed before I replied.. Thanks for the follow up. > Mark Martin wrote: >> James Walker wrote: > >>> >>> 3.4.5 Passwords >>> (see >>> http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ >>> and >>> >>> http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ >>> for details) >>> Do any of the components for the project deal with passwords? >>> [ ] Yes >>> [*] No - continue to next section (section 3.4.6) >>> >> The mysql driver support isn't included? This is in conflict with >> your clarification on question 3.5 isn't it? If it is included, is >> it important to note that the user/pass are specified on the command >> line? > The mysql driver uses a thin shim that uses libmysql to talk to the > mysql database. You are correct that it does indeed deal with > passwords and that they are specified on the command line. The > general use I've seen is to use the default username and have no set > password but that is not required. So the important thing to note here is that it does potentially use passwords, but they're not stored, and they're transmitted and used in the same manner as other mysql commands might use it (i.e. it can be specified on the command line, goes over the wire encrypted, etc) > > >>> >>> 4.0 Interfaces >>> 4.1 Exported Interfaces >>> Interface Name Classification Comments >>> ---------------- ------------------- >>> --------------------------- >>> SUNWsysbench Uncommitted Package >>> >>> /usr/benchmarks/sysbench/sysbench >>> Uncommitted Executable binary file >>> >> >> PSARC 2007/448 set the precedent that this should probably be >> /usr/benchmarks/sysbench/bin/sysbench >> > Understood, and I'll make the change. I had been distracted by PSARC > 2008/461 (bonnie++) which did not use the bin directory. Should I > also add a symlink in /usr/bin as in 2007/461? beats me. That's a closed case. :) Personally, I think "/usr/benchmarks/sysbench/bin/sysbench" is a bit mealy mouthed. I'm not sure why it's not "/usr/benchmarks/bin/sysbench", but it looked like the discussion was long and somewhat heated, so I'm sure it's the best call made by smarter folks than me. Now, though, I'm kinda curious what came out in 2007/461 ... From James.Walker@sun.com Tue Jun 23 01:07:23 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n5N87MCQ016974 for ; Tue, 23 Jun 2009 01:07:23 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n5N87LjG005840; Tue, 23 Jun 2009 09:07:22 +0100 (BST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KLO00223MK9ZB00@nwk-avmta-1.sfbay.Sun.COM>; Tue, 23 Jun 2009 01:07:21 -0700 (PDT) Received: from brmea-mail-4.sun.com ([192.18.98.36]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KLO007UJMK7BE90@nwk-avmta-1.sfbay.Sun.COM>; Tue, 23 Jun 2009 01:07:19 -0700 (PDT) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n5N87Jw0024407; Tue, 23 Jun 2009 08:07:19 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KLO00I00M9V2F00@mail-amer.sun.com>; Tue, 23 Jun 2009 02:07:19 -0600 (MDT) Received: from c-67-166-22-238.hsd1.co.comcast.net ([unknown] [129.150.33.20]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KLO000SPMK7UQ90@mail-amer.sun.com>; Tue, 23 Jun 2009 02:07:19 -0600 (MDT) Date: Tue, 23 Jun 2009 02:07:19 -0600 From: Jim Walker Subject: Re: sysbench [PSARC/2009/351 FastTrack timeout 06/18/2009] In-reply-to: <4A3A67B0.50608@gmail.com> Sender: James.Walker@sun.com To: Peter Rival Cc: psarc-ext@sun.com Reply-to: James.Walker@sun.com Message-id: <4A408D37.3000500@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200906120357.n5C3vWRZ022210@sac.sfbay.sun.com> <4A36A4D1.20600@gmail.com> <4A39AF54.3090807@sun.com> <4A3A67B0.50608@gmail.com> User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302) Status: RO Content-Length: 1046 Mark Martin wrote: >>>> >>>> 4.0 Interfaces >>>> 4.1 Exported Interfaces >>>> Interface Name Classification Comments >>>> ---------------- ------------------- >>>> --------------------------- >>>> SUNWsysbench Uncommitted Package >>>> >>>> /usr/benchmarks/sysbench/sysbench >>>> Uncommitted Executable binary file >>>> >>> >>> PSARC 2007/448 set the precedent that this should probably be >>> /usr/benchmarks/sysbench/bin/sysbench I would like to go with the above like filebench PSARC/2007/448. It was first and discussed extensively. Peter, If this is ok with you and there are no other comments, I would like to close this case. >> Understood, and I'll make the change. I had been distracted by PSARC >> 2008/461 (bonnie++) which did not use the bin directory. Should I >> also add a symlink in /usr/bin as in 2007/461? bonnie++ and some recent benchmarks probably should be looked at again. I may be able to take a look in a few weeks. Cheers, Jim From peter.rival@Sun.COM Tue Jun 23 12:34:33 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n5NJYWn8005078 for ; Tue, 23 Jun 2009 12:34:33 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n5NJYUaO001199 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Wed, 24 Jun 2009 03:34:32 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KLP00J07IDIIB00@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 23 Jun 2009 12:34:30 -0700 (PDT) Received: from brmea-mail-4.sun.com ([192.18.98.36]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KLP00I8PIDIDR50@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 23 Jun 2009 12:34:30 -0700 (PDT) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n5NJYUJa018126 for ; Tue, 23 Jun 2009 19:34:30 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KLP00J00I69EV00@mail-amer.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 23 Jun 2009 13:34:29 -0600 (MDT) Received: from [192.168.1.102] ([unknown] [76.118.173.225]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KLP00191IDDVGE0@mail-amer.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 23 Jun 2009 13:34:25 -0600 (MDT) Date: Tue, 23 Jun 2009 15:34:21 -0400 From: Peter Rival Subject: Re: sysbench [PSARC/2009/351 FastTrack timeout 06/18/2009] In-reply-to: <4A408D37.3000500@sun.com> Sender: frank.rival@Sun.COM To: James.Walker@Sun.COM Cc: psarc-ext@Sun.COM Message-id: <4A412E3D.2080501@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200906120357.n5C3vWRZ022210@sac.sfbay.sun.com> <4A36A4D1.20600@gmail.com> <4A39AF54.3090807@sun.com> <4A3A67B0.50608@gmail.com> <4A408D37.3000500@sun.com> User-Agent: Thunderbird 2.0.0.21 (X11/20090505) Status: RO Content-Length: 1179 Jim Walker wrote: > Mark Martin wrote: >>>>> >>>>> 4.0 Interfaces >>>>> 4.1 Exported Interfaces >>>>> Interface Name Classification Comments >>>>> ---------------- ------------------- >>>>> --------------------------- >>>>> SUNWsysbench Uncommitted Package >>>>> >>>>> /usr/benchmarks/sysbench/sysbench >>>>> Uncommitted Executable binary file >>>>> >>>> >>>> PSARC 2007/448 set the precedent that this should probably be >>>> /usr/benchmarks/sysbench/bin/sysbench > > I would like to go with the above like filebench PSARC/2007/448. > It was first and discussed extensively. > > Peter, > > If this is ok with you and there are no other comments, > I would like to close this case. > I'm fine with that. I'll update the code shortly. Thanks! - Pete >>> Understood, and I'll make the change. I had been distracted by >>> PSARC 2008/461 (bonnie++) which did not use the bin directory. >>> Should I also add a symlink in /usr/bin as in 2007/461? > > bonnie++ and some recent benchmarks probably should be > looked at again. I may be able to take a look in a > few weeks. > > Cheers, > Jim From James.Walker@sun.com Tue Jun 23 12:52:47 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n5NJqkGY005772 for ; Tue, 23 Jun 2009 12:52:46 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n5NJqWF1018268; Tue, 23 Jun 2009 20:52:45 +0100 (BST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KLP00L05J7WSI00@nwk-avmta-1.sfbay.Sun.COM>; Tue, 23 Jun 2009 12:52:44 -0700 (PDT) Received: from brmea-mail-1.sun.com ([192.18.98.31]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KLP00IF9J7VDRF0@nwk-avmta-1.sfbay.Sun.COM>; Tue, 23 Jun 2009 12:52:43 -0700 (PDT) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n5NJqhho002683; Tue, 23 Jun 2009 19:52:43 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KLP00700HOQRJ00@mail-amer.sun.com>; Tue, 23 Jun 2009 13:52:43 -0600 (MDT) Received: from [172.20.25.153] ([unknown] [172.20.25.153]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KLP00AFLJ7KHWB0@mail-amer.sun.com>; Tue, 23 Jun 2009 13:52:33 -0600 (MDT) Date: Tue, 23 Jun 2009 14:07:49 -0600 From: Jim Walker Subject: Re: sysbench [PSARC/2009/351 FastTrack timeout 06/18/2009] In-reply-to: <200906120357.n5C3vWRZ022210@sac.sfbay.sun.com> Sender: James.Walker@sun.com To: PSARC-ext@sun.com Cc: peter.rival@sun.com Reply-to: James.Walker@sun.com Message-id: <4A413615.9030408@sun.com> Organization: Sun Microsystems, Inc. MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200906120357.n5C3vWRZ022210@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.14 (X11/20080728) Status: RO Content-Length: 134 All comments for this case have been addressed and the timeout has been reached. I'm marking this case closed approved. Cheers, Jim