On 17/05/24 15:04, Steven Levine wrote:

In <list-9676816@2rosenthals.com>, on 05/17/24 at 10:02 AM, "Peter
Moylan" <ecs-isp@2rosenthals.com> said:

Hi Peter,

I just used a text editor to modify inetcfg.ini. (It's a plain
text file, not an INI file.) Is there anything wrong with doing it
that way?

Editing by hand is OK, as long as you don't make a typo.  The file
format is typical unix style tab separated fields.

You will need to

inetcfg -s all

to activate your changes.  When you reboot this is done by code in
\tcpip\bin\b4tcp.cmd.

Thanks. I did that last command just now. I had intended to wait for the
reboot, but I didn't get a "server hang" until today. (Couldn't fetch
mail, but luckily I could contact VNC server.) When I did a "netstat -s"
I found a large number of sockets in a CLOSE_WAIT condition, mostly on
port 22. Then I looked at SFTPServer (which uses port 22), and saw that
it was stuck in a "too many users" condition.

So the problem was with SFTPServer, not with Weasel and not with bind.
Not too surprising, since I already knew that I was getting lots of
attacks on SFTPServer, obviously people trying to break in to SSH.

When I killed and restarted SFTPServer, the mail started flowing again.