分类: Linux系统

  • Nginx 配置文件

    nginx配置样例:

    location ~ \.php$ {
    root           html;
    fastcgi_pass   127.0.0.1:9000;
    fastcgi_index  index.php;
    fastcgi_param  SCRIPT_FILENAME  $document_root$fastcgi_script_name;
    include        fastcgi_params;
    }
    # A virtual host using mix of IP-, name-, and port-based configuration
    #

    server {
    listen       80;
    server_name  mypiao.mypiao.com;

    #charset koi8-r;

    #access_log  logs/host.access.log  main;

    location ~.*\.(jpg|png|jpeg)$
    {
    root /software;
    expires 1d;
    }

    location  /mygladmin/ {
    root   /usr/share/nginx/html/xxxxxxxx;
    index index.php;
    if ( !-e $request_filename )
    {
    rewrite ^/mygladmin/(.*)$   /mygladmin/index.php/$1 last;
    break;
    }

    }

    location  /newadmin/ {
    root   /usr/share/nginx/html/xxxxxxxx;
    index index.php;
    if ( !-e $request_filename )
    {
    rewrite ^/newadmin/(.*)$   /newadmin/index.php/$1 last;
    break;
    }

    }

    location / {
    root   /usr/share/nginx/html/xxxxxxxx;
    if ( !-e $request_filename )
    {
    rewrite ^(.*)$ index.php/$1 last;
    break;
    }
    index  index.php index.html index.htm;
    }

    location ~ \.php{
    root   /usr/share/nginx/html/xxxxxxxx;
    fastcgi_index index.php;
    fastcgi_pass 127.0.0.1:9000;
    include      fastcgi_params;
    set $path_info “”;
    set $real_script_name $fastcgi_script_name;
    if ($fastcgi_script_name ~ “^(.+?\.php)(/.+)$”) {
    set $real_script_name $1;
    set $path_info $2;
    }
    fastcgi_param SCRIPT_FILENAME /usr/share/nginx/html/xxxxxxxx/$real_script_name;
    fastcgi_param SCRIPT_NAME $real_script_name;
    fastcgi_param PATH_INFO $path_info;
    }

  • /lib/ld-linux.so.2: bad ELF interpreter: 没有那个文件或目录

    yum install glibc glibc.i686

    原因是在64位系统下运行了32位的程序

    加上对应的包就好

     

  • IIS7无法显示页面,因为发生内部服务器错误。错误代码0x800700c1

    模块 IsapiModule 通知 ExecuteRequestHandler 处理程序 AboMapperCustom-532187 错误代码 0x800700c1
    经查找,找到解决方法,原来是应用程序池的问题:
    1、进入IIS中的应用程序池
    2、选中网站使用的应用程序池名称,然后点击“高级设置”,
    3、启用32位应用程序池即可!

    X64 下需要把midas.dll和dbexpint.dll 放到Windows\system 目录下

  • Bugzilla发送邮件

    本人的BUGZILLA版本是3.6的。
    关于bugzilla的发送邮件问题,在网上查了很多,有的用sendmail..等第三方邮件发送,有的在email.ini里面修改代码,这些方法我都试过,都行不通。然后我看官网的说明,BUGZILLA里自带的有SMTP,只要SMTP能够通过认证就可以了,所以第三方,以及代码什么都不用修改,只要设置params里面的参数就可以了!
    在..\data\params设置如下参数:
    maintainer :                  swaiwai@163.com
    mail_delivery_method :         SMTP
    mailfrom :                     swaiwai@163.com
    sendmailnow:                   on
    smtpserver :                   smtp.163.com
    smtp_username:                 swaiwai@163.com
    smtp_password :                **********
    注意:maintainer、mailfrom必须相同!smtp_username邮箱必须是存在的真实的邮箱,smtp_password必须是你真实邮箱的真实密码(要与你所登陆邮箱时的密码相同)!
    由与邮件问题在网上一直未看到解决方法,所以我就把我的方法给大家共享一下!(若转就注明原创!)哈哈!本人就是这样设置的,邮件已经发送成功!如果还有不能连接等问题,只能说明你的邮箱和密码有问题!

    disable_plaintext_auth = no
    ssl = no

    No success on command[/usr/bin/perl Makefile.PL  LIB=”/var/www/html/bugzilla/lib” INSTALLMAN1DIR=”/var/www/html/bugzilla/lib/man/man1″ INSTALLMAN3DIR=”/var/www/html/bugzilla/lib/man/man3″ INSTALLBIN=”/var/www/html/bugzilla/lib/bin” INSTALLSCRIPT=”/var/www/html/bugzilla/lib/bin” INSTALLDIRS=perl]
    PHRED/mod_perl-2.0.8.tar.gz
    /usr/bin/perl Makefile.PL  LIB=”/var/www/html/bugzilla/lib” INSTALLMAN1DIR=”/var/www/html/bugzilla/lib/man/man1″ INSTALLMAN3DIR=”/var/www/html/bugzilla/lib/man/man3″ INSTALLBIN=”/var/www/html/bugzilla/lib/bin” INSTALLSCRIPT=”/var/www/html/bugzilla/lib/bin” INSTALLDIRS=perl — NOT OK
    Skipping test because of notest pragma
    Running make install
    Make had some problems, won’t install
    Could not read metadata file. Falling back to other methods to determine prerequisites

  • CentOS 6.x安装第三方软件库epel

    rpm -q epel-release
    package epel-release is not installed
    如果没有安装,则install:
    rpm -ivh
    x64
    http://mirrors.ustc.edu.cn/fedora/epel/6/x86_64/epel-release-6-8.noarch.rpm
    x86
    http://mirrors.ustc.edu.cn/fedora/epel/6/i386/epel-release-6-8.noarch.rpm

    rpm –import /etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-6

    yum install yum-priorities

    cd /etc/yum.repos.d/
    ls |grep epel
    epel.repo
    epel-testing.rep

  • cpuminer

    cpu挖矿, 优化版cpuminer

    cpu挖矿, 请下载优化版的cpuminer Binaries for Windows:
    http://sourceforge.net/projects/cpuminer/files/pooler-cpuminer-2.3.2-win32.zip (32-bit)
    http://sourceforge.net/projects/cpuminer/files/pooler-cpuminer-2.3.2-win64.zip  (64-bit)
    Binaries for Linux:
    http://sourceforge.net/projects/cpuminer/files/pooler-cpuminer-2.3.2-linux-x86.tar.gz (x86)
    http://sourceforge.net/projects/cpuminer/files/pooler-cpuminer-2.3.2-linux-x86_64.tar.gz (x86-64)
    Installing dependencies for building on Debian, Ubuntu and other APT-based distros:
    $ sudo apt-get install build-essential libcurl4-openssl-dev
    Installing dependencies for building on Fedora, RHEL, CentOS and other yum-based distros:
    $ sudo yum install gcc make curl-devel
    Installing dependencies for building on OpenSUSE and other ZYpp-based distros:
    $ sudo zypper in gcc make libcurl-devel
    Recipe for building on Linux:
    $ wget http://sourceforge.net/projects/cpuminer/files/pooler-cpuminer-2.3.2.tar.gz
    $ tar xzf pooler-cpuminer-*.tar.gz
    $ cd cpuminer-*
    $ ./configure CFLAGS="-O3"
    $ make
    Basic usage examples
    $  ./minerd --url=stratum+tcp://stratum.waltc.net:3333 --userpass=LeorFUe6YBzDWerYdBRcYxquE9b8YhpTUe.ltb-server14:12345678
    $  ./minerd --url=stratum+tcp://myminingpool.com:3333 --userpass=my.worker:password
    For more information:
    $ ./minerd --help
    Just redirect the standard error stream to file: minerd [OPTIONS] 2> myfile

  • Stale file handle mount故障

    ls /mnt/ -l
    ls: cannot access /mnt/mysqldata: Stale file handle
    total 0
    d????????? ? ? ? ? ? mysqldata
    cannot stat `/mnt/mysqldata’: Stale file handle
    df
    df: `/mnt/mysqldata’: Stale file handle

    解决:

    umount -f /mnt/mysqldata
    ls /mnt/ -l
    total 4
    drwxrwxrwx 2 root root 4096 Sep 23 10:20 mysqldata

  • 不重启Linux服务器关闭SeLinux的方法

    不重启Linux服务器关闭SeLinux的方法 – 安全设置

    以下介绍一下SELinux相关的工具 /usr/bin/setenforce 修改SELinux的实时运行模式 setenforce 1 设置SELinux 成为enforcing模式 setenforce 0 设置SELinux 成为permissive模式 如果要彻底禁用SELinux 需要在/etc/sysconfig/selinux中设置参数selinux=0 ,或者在/etc/grub.conf中添加这个参数 /usr/bin/setstatus -v 不想重启服务器,有以下解决办法: 执行命令:setenforce 0 就可以不重启关闭selinux了

  • Apache并发处理模块

     

    查看连接数和当前的连接数,分别是
    netstat -ant | grep $ip:80 | wc -l
    netstat -ant | grep $ip:80 | grep EST | wc -l

    ThreadsPerChild 每个子进程的服务线程数目 默认值25
    StartServers apache启动的时候就开启的子进程数 默认值3
    MinSpareThreads 最小空闲线程数 默认值75
    MaxSpareThreads 最大空闲线程数,apache在运行的时候会让总的空闲线程数保持在MinSpareThreads和MaxSpareThreads之间,这两个参数用默认值就可以了,一般情况下没必要去调整它们 默认值250
    MaxClients 最大客户端并发处理数(最大线程数),MaxClients除以ThreadsPerChild得到的值的就是最大可能达到的子进程数,如果服务器的并发请求数超过了MaxClients,那么apache会报这样的错误:server reached MaxClients setting, consider raising the MaxClients setting 默认值16*25 = 400
    ServerLimit 最大进程数限制,这个参数值必须大于或等于MaxClients除以ThreadsPerChild得到的值。这个参数是硬限制,直接重启apache(apache restart)不会生效,必须先停止apache(apache stop)再启动apache(apache start)才生效 worker模式下默认值是16,prefork模式则是256
    ThreadLimit 每个进程的最大线程数限制,也就是说这个参数决定了ThreadsPerChild的最大值。如果这个参数设得比ThreadsPerChild大很多的话,那么会浪费掉很多共享内存。设置过大还可能会导致apache无法启动或者系统不稳定。这个参数也是硬限制。如果要设置的话,ServerLimit和ThreadLimit必须放在其它设置的前面 默认值64
    MaxRequestsPerChild 单个子进程在其生命周期内处理的总请求数限制,当某个子进程处理过的总请求数到达这个限制后这个进程就会被回收,如果设为0,那么这个进程永远不会过期(这样如果有内存泄露的话就会一直泄露下去……)

    <IfModule prefork.c>
    StartServers 10
    MinSpareServers 10
    MaxSpareServers 15
    ServerLimit 2000
    MaxClients 1500
    MaxRequestsPerChild 10000
    </IfModule>

    ServerLimit 要放在 MaxClients 前面!!!

    另外,調整之後如果以 apachectl graceful 重開 Apache,ServerLimit 的設定並不會生效,log 檔裡會出現以下的錯誤訊息:

    [Wed Aug 11 22:31:41 2009] [warn] WARNING: Attempt to change ServerLimit ignored during restart
    如果以 apachectl restart 重開也沒用,一樣會出現前面提過的錯誤訊息:
    WARNING: MaxClients of 300 exceeds ServerLimit value of 256 servers,
    lowering MaxClients to 256.  To increase, please see the ServerLimit
    directive.
    在前面提過的官網說明中有一段隱晦的說明:

    Any attempts to change this directive during a restart will be ignored, but MaxClients can be modified during a restart.
    因此要使 ServerLimit 生效,必須先停止 Apache: apachectl stop,再開啟 Apache: apachectl start

    Apache中MaxRequestsPerChild参数及配置

    MaxRequestsPerChild这个指令设定一个独立的子进程将能处理的请求数量。
    在处理 “MaxRequestsPerChild”请求之后,子进程将会被父进程终止,这时候子进程占用的内存就会释放,如果再有访问请求,父进程会重新产生子进程进行处理。
    如果 MaxRequestsPerChild缺省设为0(无限)或较大的数字(例如10000以上)可以使每个子进程处理更多的请求,不会因为不断终止、启动子进程降低访问效率,
    但MaxRequestsPerChild设置为0时,如果占用了200~300M内存,即使负载下来时占用的内存也不会减少。内存较大的服务器可以设置为0或较大的数字。内存较小的服务器不妨设置成30、50、100,以防内存溢出

     

  • httpd dead but pid file exists

    httpd dead but pid file existsApache起不来,报No space left on device: Couldn’t create accept lock
    service httpd restart
    提示正常
    service httpd status
    提示:httpd dead but pid file exists
    检查80端口是否被占用
    netstat -tulpn | grep :80
    没有记录
    继续
    rm /var/lock/subsys/httpd
    rm /var/run/httpd/httpd.pid
    service httpd restart
    还是提示:httpd dead but pid file exists
    检查 /var/log/httpd/error_log
    发现 [emerg] (28)No space left on device: Couldn’t create accept lock (/etc/httpd/logs/accept.lock.13255) (5)
    以为是空间不足,造成无法创建锁文件,但是df -h察看,发觉不是这个问题。
    google 一下
    ipcs -s
    —— Semaphore Arrays ——–
    key        semid      owner      perms      nsems
    0x000000a7 0          root      600        1
    0x00000000 32769      apache    600        1
    0x00000000 65538      apache    600        1
    0x00000000 884739     apache    600        1
    0x00000000 917508     apache    600        1

    一大堆的ipc使用,需要干掉。
    清除命令
    for semid in `ipcs -s | grep apache | cut -f2 -d” “`;
    do ipcrm -s $semid; done
    service httpd restart
    service httpd status
    提示正常

    查看the number of semaphores that are available on the system

    admin@intlqa142012x:[/home/admin]ipcs -l

    —— Shared Memory Limits ——–
    max number of segments = 4096
    max seg size (kbytes) = 32768
    max total shared memory (kbytes) = 8388608
    min seg size (bytes) = 1

    —— Semaphore Limits ——–
    max number of arrays = 128
    max semaphores per array = 250
    max semaphores system wide = 32000
    max ops per semop call = 32
    semaphore max value = 32767

    —— Messages: Limits ——–
    max queues system wide = 16
    max size of message (bytes) = 8192
    default max size of queue (bytes) = 16384

    如果有权限的话,可以修改这些限制:
    To change these parameters, modify the file /etc/sysctl.conf and add the following lines:

    kernel.msgmni = 1024
    kernel.sem = 250 256000 32 1024

    Then load these settings with the command:sysctl -p
    -p Load in sysctl settings from the file specified or /etc/sysctl.conf if none given.

    admin@intlqa142012x:[/home/admin]sysctl -p
    error: permission denied on key ‘net.ipv4.ip_forward’
    error: permission denied on key ‘net.ipv4.conf.default.rp_filter’
    error: permission denied on key ‘net.ipv4.conf.default.accept_source_route’
    error: permission denied on key ‘kernel.sysrq’
    error: permission denied on key ‘kernel.core_uses_pid’

    Your Apache process should now be able to create the needed semaphores and run properly.

    说明:kernel.msgmni
    该文件指定消息队列标识的最大数目,即系统范围内最大多少个消息队列。缺省设置:16。

    admin@intlqa142012x:[/home/admin]cat /proc/sys/kernel/msgmni
    16

    在root下可用sysctl kernel.msgmni检查该参数:

    admin@intlqa142012x:[/home/admin]sysctl kernel.msgmni
    kernel.msgmni = 16

    也可以在命令行下,使用sysctl -w kernel.msgmni=XXX重新设定。

    admin@intlqa142012x:[/home/admin]sysctl -w kernel.msgmni=32
    error: permission denied on key ‘kernel.msgmni’

     

     

    ipcs 命令

    ipcs – 分析消息队列、共享内存和信号量
    ipcs – report status of interprocess communication facilities

    ipcs displays certain information about active interprocess communication facilities. With no options, ipcs displays information in short format for the message queues, shared memory segments, and semaphores that are currently active in the system.

    引用

    它的语法:

    ipcs [-mqs] [-abcopt] [-C core] [-N namelist]
    -m 输出有关共享内存(shared memory)的信息
    -q 输出有关信息队列(message queue)的信息
    -s 输出信号量(semaphore)的信息
    # ipcs -m
    IPC status from as of 2007年04月10日 星期二 18时32分18秒 CST
    T ID KEY MODE OWNER GROUP
    Shared Memory:
    m 0 0x50000d43 –rw-r–r– root root
    m 501 0x1e90c97c –rw-r—– oracle dba

    ipcrm – 删除ipc(清除共享内存信息)

    引用
    它的语法:
    ipcrm -m|-q|-s shm_id
    -m 输出有关共享内存(shared memory)的信息
    -q 输出有关信息队列(message queue)的信息
    -s 输出信号量(semaphore)的信息
    shm_id 共享内存id
    #ipcrm -m 501


    ipcs用于显示消息队列、共享内存、信号灯信息的
    q 显示消息队列
    s 显示信号灯
    m 显示共享内存
    a 详细信息

    其打印出当前你的系统中处于活动状态的共享内存的信息。

    对每一个资源,这个命令会显示:

    TYPE        包括信息队列(q),共享内存段(m),或者信号灯(s)。

    ID         资源条目的唯一的表示号

    KEY        应用程序存取资源使用的参数。

    MODE        存取模式和许可权限的标记

    OWNER and GROUP   登录名和用户属主的组号,OnLine使用的所有的共享内存资源的属主的属主          为root和informix组。

    OnLine共享内存使用的基本键值为0x52564801。SERVERNUM的值乘上0X10000并且加上这个值就为共享内存的键值。这就 是,如果你的SERVERNUM的值为2,你的共享内存段的键值为0x52564801+(2*0x10000)=0x52584801。如果 SERVERNUM的值为6,产生的键值就为0x525c4801。
    清除命令:
    ipcs -s | grep nobody | perl -e ‘while (<STDIN>) { @a=split(/”s+/); print `ipcrm sem $a[1]`}’
    然后启动Apache即可更深入的了解:

     

    Fixing Apache “No space left on device: Couldn’t create accept lock” errors

    Error Message: When starting Apache, I get this error message in the main Apache error_log:

    [emerg] (28)No space left on device: Couldn’t create accept lock
    [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
    [notice] Digest: generating secret for digest authentication …
    [notice] Digest: done
    [warn] pid file /etc/httpd/run/httpd.pid overwritten — Unclean shutdown of previous Apache run?
    [emerg] (28)No space left on device: Couldn’t create accept lock

    First off, check to make sure that you really aren’t out of disk space, or have hit a quota limit. Another way that Apache can create the “accept lock” is with a semaphore. A semaphore is an inter-process communication tool that is used by Apache to communicate with it’s child processes. This error message may mean that Apache couldn’t create a new semaphore.

    Check to see how many semaphores are currently in use. If Apache is running correctly, you should see something like this:

    # ipcs -s
    —— Semaphore Arrays ——–
    key semid owner perms nsems
    0x00000000 68681743 apache 600 1
    0x00000000 68714515 apache 600 1
    0x00000000 68747291 apache 600 1

    If Apache is stopped, and you still see these semaphores, then you can safely kill them by running this command for each semaphore id (in the second column)

    $ ipcrm -s <semid>

    To destroy all semaphores, you can run this from the command line (with “apache” being the apache-user):

    for semid in `ipcs -s | grep nobody | cut -f2 -d” “`;

    do ipcrm -s $semid; done

    If you are out of semaphores

    If you can’t create any more semaphores:

    Sometimes your system may need to increase the number of semaphores that are available on the system. This requires a change to a kernel parameter. If you are running on a virtual server and cannot modify kernel parameters, you may need to ask your hosting provider to change this parameter on their host server To view the current parameters:

    # ipcs -l
    —— Shared Memory Limits ——–
    max number of segments = 4096
    max seg size (kbytes) = 32768
    max total shared memory (kbytes) = 8388608
    min seg size (bytes) = 1

    —— Semaphore Limits ——–
    max number of arrays = 1024
    max semaphores per array = 250
    max semaphores system wide = 256000
    max ops per semop call = 32
    semaphore max value = 32767

    —— Messages: Limits ——–
    max queues system wide = 1024
    max size of message (bytes) = 8192
    default max size of queue (bytes) = 16384

    To change these parameters, modify the file /etc/sysctl.conf and add the following lines:

    kernel.msgmni = 1024
    kernel.sem = 250 256000 32 1024

    Then load these settings with the command:

    sysctl -p

    Your Apache process should now be able to create the needed semaphores and run properly

    这里介绍下kernel.msgmni

    /proc/sys/kernel/msgmni

    该文件指定消息队列标识的最大数目,即系统范围内最大多少个消息队列。
    缺省设置:16

    在 root 下用 sysctl kernel.msgmni 检查该参数, 也可以在命令行下

    sysctl -w kernel.msgmni=XXX 重新设定。

    man ipcs:

    ipcs(1)                                                              ipcs(1)

    NAME
    ipcs – report status of interprocess communication facilities

    SYNOPSIS
    ipcs [-mqs] [-abcopt] [-C core] [-N namelist]

    DESCRIPTION
    ipcs displays certain information about active interprocess
    communication facilities.   With no options, ipcs displays information
    in short format for the message queues, shared memory segments, and
    semaphores that are currently active in the system.

         Options
    The following options restrict the display to the corresponding
    facilities.

                (none)          This is equivalent to -mqs.

                -m              Display information about active shared memory
    segments.
    -q              Display information about active message queues.

                -s              Display information about active semaphores.

           The following options add columns of data to the display.   See “Column
    Description” below.

                (none)          Display default columns: for all facilities: T,
    ID, KEY, MODE, OWNER, GROUP.

                -a              Display all columns, as appropriate.   This is
    equivalent to -bcopt.

                -b              Display largest-allowable-size information: for
    message queues: QBYTES; for shared memory
    segments: SEGSZ; for semaphores: NSEMS.

                -c              Display creator’s login name and group name: for
    all facilities: CREATOR, CGROUP.

                -o              Display information on outstanding usage: for
    message queues: CBYTES, QNUM; for shared memory
    segments: NATTCH.

                -p              Display process number information: for message
    queues: LSPID, LRPID; for shared memory segments:
    CPID, LPID.

                -t              Display time information: for all facilities:
    CTIME; for message queues: STIME, RTIME; for

    Hewlett-Packard Company             – 1 –    HP-UX Release 11i: November 2000

    ipcs(1)                                                              ipcs(1)

                               shared memory segments: ATIME, DTIME; for
    semaphores: OTIME.

           The following options redefine the sources of information.

                -C core         Use core in place of /dev/kmem.   core can be a
    core file or a directory created by savecrash or
    savecore.

                -N namelist     Use file namelist or the namelist within core in
    place of /stand/vmunix.   It opens a crash dump for
    reading. Please refer to cr_open(3) for more
    details.

         Column Descriptions
    The column headings and the meaning of the columns in an ipcs listing
    are given below.   The columns are printed from left to right in the
    order shown below.

                T          Facility type:

                               m     Shared memory segment
    q     Message queue
    s     Semaphore

                ID         The identifier for the facility entry.

                KEY        The key used as an argument to msgget(), semget(), or
    shmget() to create the facility entry.   (Note: The key
    of a shared memory segment is changed to IPC_PRIVATE
    when the segment has been removed until all processes
    attached to the segment detach it.)
    MODE       The facility access modes and flags: The mode consists
    of 11 characters that are interpreted as follows:

                          The first two characters can be:

                               R     A process is waiting on a msgrcv().
    S     A process is waiting on a msgsnd().
    D     The associated shared memory segment has been
    removed.   It will disappear when the last
    process attached to the segment detaches it.
    C     The associated shared memory segment is to be
    cleared when the first attach is executed.
    –     The corresponding special flag is not set.

                          The next 9 characters are interpreted as three sets of
    three characters each.   The first set refers to the
    owner’s permissions, the next to permissions of others
    in the group of the facility entry, and the last to all

    Hewlett-Packard Company             – 2 –    HP-UX Release 11i: November 2000
    ipcs(1)                                                              ipcs(1)

                          others.

                          Within each set, the first character indicates
    permission to read, the second character indicates
    permission to write or alter the facility entry, and
    the last character is currently unused.

                               r     Read permission is granted.
    w     Write permission is granted.
    a     Alter permission is granted.
    –     The indicated permission is not granted.

                OWNER      The login name of the owner of the facility entry.

                GROUP      The group name of the group of the owner of the
    facility entry.

                CREATOR    The login name of the creator of the facility entry.

                CGROUP     The group name of the group of the creator of the
    facility entry.

                CBYTES     The number of bytes in messages currently outstanding
    on the associated message queue.

                QNUM       The number of messages currently outstanding on the
    associated message queue.

                QBYTES     The maximum number of bytes allowed in messages
    outstanding on the associated message queue.

                LSPID      The process ID of the last process to send a message to
    the associated message queue.

                LRPID      The process ID of the last process to receive a message
    from the associated message queue.

                STIME      The time the last msgsnd() message was sent to the
    associated message queue.

                RTIME      The time the last msgrcv() message was received from
    the associated message queue.

                CTIME      The time when the associated facility entry was created
    or changed.

                NATTCH     The number of processes attached to the associated
    shared memory segment.

                SEGSZ      The size of the associated shared memory segment.

    Hewlett-Packard Company             – 3 –    HP-UX Release 11i: November 2000

    ipcs(1)                                                              ipcs(1)

                CPID       The process ID of the creating process of the shared
    memory segment.

                LPID       The process ID of the last process to attach or detach
    the shared memory segment.

                ATIME      The time the last shmat() attach was completed to the
    associated shared memory segment.

                DTIME      The time the last shmdt() detach was completed on the
    associated shared memory segment.

                NSEMS      The number of semaphores in the set associated with the
    semaphore entry.

                OTIME      The time the last semop() semaphore operation was
    completed on the set associated with the semaphore
    entry.

    WARNINGS
    ipcs produces only an approximate indication of actual system status
    because system processes are continually changing while ipcs is
    acquiring the requested information.

           Do not rely on the exact field widths and spacing of the output, as
    these will vary depending on the system, the release of HP-UX, and the
    data to be displayed.

    FILES
    /dev/kmem            Kernel virtual memory
    /etc/group           Group names
    /etc/passwd          User names
    /stand/vmunix        System namelist
    SEE ALSO
    msgop(2), semop(2), shmop(2).

    STANDARDS CONFORMANCE
    ipcs: SVID2, SVID3

    Hewlett-Packard Company             – 4 –    HP-UX Release 11i: November 2000