On Thu, 15 Feb 2001, Steven W. Orr wrote:
> Generally speaking, no. But since you're running Linux you could probably
> try to get involved in debugging the kernel :-(
>
> Another way to figure it out is to rebuild your kernel without ipc
> support. Then when somebody tried to perform one of the three possible
> create operations, it should fail and hopefully report back to you. BTW, I
> consider it a mark of bad programming to create ipcs in such a way that
> they are left around after the program has exited.
Why would that be ? Interprocess Communication does not necessarily require
that all of the communicating processes exist at the same time. I know of at
least one database product that does this VERY deliberately.
>
>
> --
> -Time flies like the wind. Fruit flies like a banana. Stranger things have -
> -happened but none stranger than this. Does your driver's license say Organ
> -Donor?Black holes are where God divided by zero. Listen to me! We are all-
> -individuals! What if this weren't a hypothetical question? [EMAIL PROTECTED]
>
>
> On Thu, 15 Feb 2001, Benjamin Scott wrote:
>
> =>Hello list,
> =>
> => Does anyone here know of a way to find out which program created a System V
> =>IPC resource? I am aware of ipcs(8), but it will only tell you the PID, not
> =>the actual program. And if the creating program has since exited, the PID is
> =>not very useful. I'd like to know what all these IPC resources floating
> =>around on some systems are.
> =>
> => The distro is Red Hat 6.2, if that matters.
> =>
> =>
>
>
> **********************************************************
> To unsubscribe from this list, send mail to
> [EMAIL PROTECTED] with the following text in the
> *body* (*not* the subject line) of the letter:
> unsubscribe gnhlug
> **********************************************************
--
There's no such thing as a "pretty good" alligator wrestler.
[EMAIL PROTECTED] Tom Rauschenbach
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
