ok sad to report the telnetd locking still happens with manually killing btagent, I had my modem powered on in this room for over a week, tried telnet today and needed to reboot to access.
if I run top, there is an indication of whats wrong.
At first the process called autbtex was consuming all cpu power, I couldnt kill it, its unkillable.
Now that process is fighting with telnetd for all cpu power.
the modem has a load avg of over 4.xx just sitting idle on my lan.
so somethign is sucking up cpu power and I expect also sucking up resources probably eventually causing telnet to lockup. The one process that is consistent is autbtex, telnet isnt constantly sucking up cpu power it goes idle after a bit of time.
I want to get an ECI running on my line now, as I am currently interleaved, last time I was it recovered in 2 days with prety much no errors, but it seems there is complications this time round, the hg lost sync about 2 hours ago (which is probably going to trash DLM recovery) and the only cause is I can see a short period of lower upload attainable (still above 20meg) which coincided with the resync, the modem actually synced higher than previous suggesting it was a very short issue that had gone by the time it had synced, so I want to see if ECI fixes these niggling issues as DLM is a pain. But I am not keen plugging in a modem that has issues with processes sucking up all its cpu power whilst idle and a telnet that will lock me out after a few days.
My new ECI v1 seems to have been sent via a dodgy courier so I am not sure when I will get it now.