Re: Hotplug and unloading modules

2002-12-29 Thread Bill Moseley
What causes a module to be "used" and can I find out what is using it? And is there a way to force a module to be unloaded? What is happening is jpilot-sync is causing the visor "used" count to increment which then prevents the modules from unloading: # lsmod Module Size Used b

Re: Hotplug and unloading modules

2002-12-28 Thread Bill Moseley
On Thu, 26 Dec 2002, Marc Wilson wrote: > On Thu, Dec 26, 2002 at 06:11:06PM -0800, Bill Moseley wrote: > > Is there a way to either unload the modules automatically on hotplug > > disconnect so that it will run my script again on next hotsync? > > Sure. Just have your action script unload it ex

Re: Hotplug and unloading modules

2002-12-27 Thread Bill Moseley
On Thu, 26 Dec 2002, Marc Wilson wrote: > On Thu, Dec 26, 2002 at 06:11:06PM -0800, Bill Moseley wrote: > > Is there a way to either unload the modules automatically on hotplug > > disconnect so that it will run my script again on next hotsync? > Sure. Just have your action script unload it expl

Re: Hotplug and unloading modules

2002-12-26 Thread Marc Wilson
On Thu, Dec 26, 2002 at 06:11:06PM -0800, Bill Moseley wrote: > This works fine the first time, but then the visor module is left > installed. The problem is that the next time hotsync button is pushed the > usb.agent script runs again, but since the visor module is already loaded > /etc/hotplug/u