l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2002 Jun 18 15:13

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] Question about listing loaded modules by process...
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] Question about listing loaded modules by process...

On Mon, Jun 17, 2002 at 03:49:24PM -0700, R. Douglas Barbieri wrote:
> Isn't there a program out there, a la lsmod and lsof, which allows me to
> list what processes are requiring the use of what OS device modules? In
> other words, to list out the fact that "play" has "sb.o" locked into
> memory?

  I don't know of anything that allows a lookup of what raised the
use count on a loaded kernel module.  It would be useful for lsmod, 
rmmod, or modprobe to be able to print this information out.

  I imagine if it were easy to do it would have been done already...
but I would file a bug against modutils if I wanted to know why it
is not possible.  :)

  Keep in mind that a process is not required to hold a kernel module
into memory.  Two simple examples are mounted filesystems will hold
that filesystem module into memory and an up eth interface will hold the
ethernet driver.
vox-tech mailing list

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
Appahost Applications
For a significant contribution towards our projector, and a generous donation to allow us to continue meeting at the Davis Library.