I don't know if anyone of you has this problem, but I found that
everytime ax25d answers a call and spawns a connection to a service it
opens "ax25" module for use. The problem is that when the connection is
closed we still have the "ax25" module opened.
This means that I can never remove ax25 module from memory because it
says it is in use.
When I made my last reboot I had ax25 module opened 725 times.
Present situation:
Module Size Used by
af_packet 5868 5 (autoclean)
scc 18168 3
mkiss 7516 1
ax25 35776 56 [scc mkiss]
call local0 cs1sel-8 cs1sel-9 (calling linuxnode via linuxnet in a local
link to linuxnet)
When the connection is up:
Module Size Used by
af_packet 5868 5 (autoclean)
scc 18168 3
mkiss 7516 1
ax25 35776 58 [scc mkiss]
I close the connection by leaving LinuxNode (bye).
After connection is closed:
Module Size Used by
af_packet 5868 5 (autoclean)
scc 18168 3
mkiss 7516 1
ax25 35776 57 [scc mkiss]
These tests were made also with CLX (CS1SEL-5) and axconv for htpp
(CS1SEL-6). No one have called to these services in the meantime.
----- " ------
Other problem found in ax25d is that when I quit linuxnet and remove the
kissattach of my local loopback link (ifconfigured), my ax25d blows and
leaves a core dump. I have to restart it again.
My sequence of commands to remove linuxnet is:
ifconfig ax0 down
kill the kissattach command
kill the linuxnet program
and at last remove the tty LOCK.
I haven't found yet where is the problem. Can I do this when I have
connections made trough this interface?
Thanks for your attention,
Jorge Matias
(CT2HBZ)
