In <list-9676200@2rosenthals.com>, on 05/16/24
at 11:19 AM, "Lewis G Rosenthal" <ecs-isp@2rosenthals.com> said:
Hi Lewis,
>inetcfg -g all
Which rewrites %ETC%\inetcfg.ini
>When the stack initializes,
>it will automatically read %ETC%\inetcfg.ini which will have keepalive
>30 in it.
Recall that this is not entirely automatic on a standard setup.
Tcpstart.cmd is run from the startup folder and optionally runs b4tcp.cmd
which contains
if exist %etc%\inetcfg.ini CALL inetcfg.exe -set all
which reads inetcfg.ini and applies the settings.
If one wants to test/modify inetcfg settings without modifying
inetcfg.ini, the inetcfg commands can be placed in tcpexit.cmd.
As you mentioned, you cannot put the inetcfg commands in startup.cmd
because they may or may not run before the commands run by tcpstart.cmd.
That said, the above does not really apply to Massimo's servers because
the does not run the WPS on his servers. He uses
SET RUNWORKPLACE=C:\OS2\CMD.EXE
and his startup.cmd implements replacements for mptn's setup.cmd and
tcpstart.cmd etc.
?????