|
NAMEshmcat - dump shared memory segments, files, standard input and/or textSYNOPSISshmcat [ OPTION ]... [ OPERAND ]...DESCRIPTIONDump shared memory segments, files, standard input and/or text to standard output. If no OPERAND is given, read standard input only. If more than one OPERAND is given, dump them in order. If some of the OPERANDs cannot be read, shmcat prints an error message to standard error and tries to continue with the other OPERANDs, unless the -S or --stop option is given.Most modern systems support two APIs for shared memory: The older one is commonly known as the System V API. It uses numeric keys and IDs as identifiers and consists of system calls like shmget(2), shmat(2) and shmdt(2). The newer API is called the POSIX shared memory API. It uses names in string form as identifiers. It treats shared memory similar to files, which are opened with shm_open(3) and then mapped into the program address space via mmap(2). Please note that POSIX shared memory is not supported by all versions of shmcat. If shmcat has been compiled without getopt_long(3) support, only the short, one character OPTIONs and OPERANDs can be used. Otherwise the long ones are also available. When a long OPTION or OPERAND needs an argument, the short versions do so, as well. OPTIONS
OPERANDS
EXIT CODES
NOTESUsually, when you dump shared memory segments, you should redirect the output of shmcat to a file or a program like od(1), because shared memory data usually has a binary form and thus it may contain non-printable characters. You also probably want to suspend the processes writing to the shared memory object in order to get a consistent dump.AUTHORStefan GastSEE ALSOftok(1), ipcs(1), shmat(2), shmget(2), shm_open(3)
Visit the GSP FreeBSD Man Page Interface. |