Hi,
A few week ago, I was complaining that the irda module usage
count was higher than 0 even after killing irattach, which would
prevent module removal. That's annoying, because everytime you
recompile IrDA, you need to reboot your box. While fixing a socket
bug, I've found the reason.
Everytime a network application is launched, it opens a IrDA
socket (that it will never use). For example, each time I start an
instance of Emacs, an IrDA socket is created, which increase the
module usage count.
Solution :
o wait until all the boot stuff is finish and idle to start
the IrDA stack (to avoid all kind of daemons opening up IrDA socket).
o before removing the stack, exit all network applications
(such as emacs, for example).
Voila...
Jean
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www.pasta.cs.UiT.No/mailman/listinfo/linux-irda
