This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: shm status
- From: Christopher Faylor <cgf at redhat dot com>
- To: cygwin-developers at cygwin dot com
- Date: Sun, 9 Jun 2002 12:36:07 -0400
- Subject: Re: shm status
- References: <072501c20fb8$8d16dc80$6132bc3e@BABEL>
- Reply-to: cygwin-developers at cygwin dot com
On Sun, Jun 09, 2002 at 02:21:22PM +0100, Conrad Scott wrote:
>Also the ipcs and ipcrm utitilities are really useful when working with sysv
>ipc so I also thought I could start by adding these. Presumably this would
>be a case for another cygwin_internal() interface? i.e. get the list of ids;
>the program then issues xxxctl() calls to get the relevant details or rm the
>requested objects. Any objections to such an approach? (Just for comparison,
>the usual Un*x implementation involves reading kernel memory via /dev/kmem.)
Do we need a cygwin_internal interface? How do OSes like linux do this?
Maybe it makes sense to start exposing things via the /proc interface, if that
is the way linux does it.
cgf