1.\" 2.\" Copyright (c) 2013 3.\" The DragonFly Project. All rights reserved. 4.\" 5.\" Redistribution and use in source and binary forms, with or without 6.\" modification, are permitted provided that the following conditions 7.\" are met: 8.\" 9.\" 1. Redistributions of source code must retain the above copyright 10.\" notice, this list of conditions and the following disclaimer. 11.\" 2. Redistributions in binary form must reproduce the above copyright 12.\" notice, this list of conditions and the following disclaimer in 13.\" the documentation and/or other materials provided with the 14.\" distribution. 15.\" 3. Neither the name of The DragonFly Project nor the names of its 16.\" contributors may be used to endorse or promote products derived 17.\" from this software without specific, prior written permission. 18.\" 19.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 20.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 21.\" LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS 22.\" FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE 23.\" COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, 24.\" INCIDENTAL, SPECIAL, EXEMPLARY OR CONSEQUENTIAL DAMAGES (INCLUDING, 25.\" BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 26.\" LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED 27.\" AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, 28.\" OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT 29.\" OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 30.\" SUCH DAMAGE. 31.\" 32.Dd January 4, 2014 33.Dt SYSVIPCD 8 34.Os 35.Sh NAME 36.Nm sysvipcd 37.Nd SysV IPC daemon 38.Sh SYNOPSIS 39.Nm 40.Op Fl df 41.Op Fl p Ar pidfile 42.Sh DESCRIPTION 43The 44.Nm 45daemon handles the resource management for the userspace implementation of 46the XSI Interprocess Communication functions. 47It is responsible for mapping shared memory, semaphores and message queues 48into the clients' address spaces and it has to be running for the 49userspace implementation to work. 50.Pp 51Clients connect to it through a 52.Ux socket . 53The daemon also monitors the 54.Xr fork 2 55system call and any children of a process using the userspace 56implementation automatically connect to the daemon too. 57.Pp 58The following options are available: 59.Bl -tag -width indent 60.It Fl d 61run in debugging mode (prints debug messages and implies 62.Fl f ) 63.It Fl f 64do not go to the background 65.It Fl p Ar pidfile 66when specified, write the process ID to 67.Ar pidfile 68instead of the default 69.Pa /var/run/sysvipcd.pid . 70.El 71.Sh ENVIRONMENT 72If the 73.Ev USR_SYSVIPC 74variable is set in a process' environment, the process and its children 75will use the userspace implementation of the XSI Interprocess Communication 76functions. 77.Sh FILES 78.Bl -tag -width ".Pa /var/run/sysvipc/sysvipc_socket" -compact 79.It Pa /var/run/sysvipc/sysvipc_socket 80name of the 81.Ux 82domain stream socket for client communication 83.El 84.Sh SEE ALSO 85.Xr msgctl 2 , 86.Xr msgget 2 , 87.Xr msgrcv 2 , 88.Xr msgsnd 2 , 89.Xr semctl 2 , 90.Xr semget 2 , 91.Xr semop 2 , 92.Xr shmat 2 , 93.Xr shmctl 2 , 94.Xr shmget 2 95.Sh HISTORY 96The 97.Nm 98daemon was added in 99.Dx 3.7 100.Sh AUTHORS 101.An Larisa Grigore 102