[go: up one dir, main page]

Menu

Tree [262cad] shmcat-1.2 /
 History

HTTPS access


File Date Author Commit
 m4 2012-02-21 Stefan Gast Stefan Gast [262cad] Initial commit
 po 2012-02-21 Stefan Gast Stefan Gast [262cad] Initial commit
 src 2012-02-21 Stefan Gast Stefan Gast [262cad] Initial commit
 .gitignore 2012-02-21 Stefan Gast Stefan Gast [262cad] Initial commit
 AUTHORS 2012-02-21 Stefan Gast Stefan Gast [262cad] Initial commit
 COPYING 2012-02-21 Stefan Gast Stefan Gast [262cad] Initial commit
 ChangeLog 2012-02-21 Stefan Gast Stefan Gast [262cad] Initial commit
 Makefile.am 2012-02-21 Stefan Gast Stefan Gast [262cad] Initial commit
 NEWS 2012-02-21 Stefan Gast Stefan Gast [262cad] Initial commit
 README 2012-02-21 Stefan Gast Stefan Gast [262cad] Initial commit
 autogen.sh 2012-02-21 Stefan Gast Stefan Gast [262cad] Initial commit
 configure.ac 2012-02-21 Stefan Gast Stefan Gast [262cad] Initial commit
 mkinstalldirs 2012-02-21 Stefan Gast Stefan Gast [262cad] Initial commit
 release.sh 2012-02-21 Stefan Gast Stefan Gast [262cad] Initial commit

Read Me

shmcat - a tool to dump System V shared memory segments, files and text
(C) 2012 by Stefan Gast <sgdev@arcor.de>

This is free software.  You may redistribute copies of it under the terms of
the GNU General Public License <http://www.gnu.org/licenses/gpl.html>.
There is NO WARRANTY, to the extent permitted by law.

License: GPLv2 or later

Report bugs to: sgdev@arcor.de

Compile and install in the usual GNU way:
	cd SUBDIR
	./configure
	make
	su -c 'make install'

To dump a shared memory segment, given by key:
	shmcat -M KEY
	(where KEY is some shared memory key obtained via ipcs (1))

To dump a shared memory segment, given by id:
	shmcat -m ID
	(where ID is some shared memory ID obtained via ipcs (1))

You can dump several segments and files together with one call, e.g.:
	shmcat -m 1234 -f some_file

For more information type:
	shmcat -h

If you dump shared memory segments, you would probably want to redirect the
output of shmcat to a file or a program like od (1), because shared memory
data is usually in a binary format and thus it may contain non-printable
characters.