Date: Mon, 26 Mar 2001 22:59:01 -0800 From: Dima Dorfman <dima@unixfreak.org> To: Andrew Hesford <ajh3@chmod.ath.cx> Cc: FreeBSD-questions <freebsd-questions@freebsd.org> Subject: Re: SysV Shared Memory Message-ID: <20010327065901.828443E09@bazooka.unixfreak.org> In-Reply-To: <20010327004920.A6193@cec.wustl.edu>; from ajh3@chmod.ath.cx on "Tue, 27 Mar 2001 00:49:20 -0600"
index | next in thread | previous in thread | raw e-mail
Andrew Hesford <ajh3@chmod.ath.cx> writes:
> Thank you, now I may RTFM.
>
> It's a bit difficult to look through manpages when you don't know what
> the command is.
Sometimes. In this case, it was quite a reasonable question (I hope
you don't get offended by ``RTFM''; IMO, you'd learn a lot more if I
told you where to find the answer rather than provide it for you).
That said, there are a few places you could look:
1) The ``SEE ALSO'' section in related manual pages. ipcs(1) lists
ipcrm(1) in its ``SEE ALSO'' section.
2) apropos(1). This is convenient if you know what the description
of the command might contain, but not what the actual command is. E.g.,
`apropos ipc` yields:
ftok(3) - create IPC identifier from path name
ipcrm(1) - remove the specified message queues, semaphore sets, and shared segments
ipcs(1) - report System V interprocess communication facilitiesstatus
mbuf(9) - memory management in the kernel IPC subsystem
perlipc(1) - Perl interprocess communication (signals, fifos, pipes, safe subprocesses, sockets, and semaphores)
IPC::Msg(3), s-1IPC:s0:Msg(3) - SysV Msg s-1IPCs0 object class
IPC::Open2(3), s-1IPC:s0:Open2(3), open2(3) - open a process for both reading and writing
IPC::Open3(3), s-1IPC:s0:Open3(3), open3(3) - open a process for reading, writing, and error handling
IPC::Semaphore(3), s-1IPC:s0:Semaphore(3) - SysV Semaphore s-1IPCs0 object class
IPC::SysV(3), s-1IPC:s0:SysV(3) - SysV s-1IPCs0 constants
As you can see, not everything is relevant, but unless you get
pages after pages of matches, it can't hurt to look through it just in
case you find what you need. In this case, ipcrm(1) jumps out as
a potential answer.
Regards
Dima Dorfman
dima@unixfreak.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010327065901.828443E09>
