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
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
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
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
I have a USB Palm m505 device. Hotplug works, but I'm trying to get it to
run a script when I push the hotsync button.
If the visor module is not loaded then hotplug runs the usb.agent script
and that loads the visor module and then runs /etc/hotplub/usb/visor,
which is where I'd then run jpilot-
5 matches
Mail list logo
