Text 26, 79 rader
Skriven 2006-04-23 08:05:20 av Peter Knapper (3:772/1.10)
     Kommentar till text 13 av Kevin Nunn (1:397/10)
Ärende: CMD file name
=====================
Hi Kevin,

 HR> When startup.cmd gets started from the system 
 HR> tcp/ip is already awaken but the peer services are not.

 KN> I seem to recall having problems with that, so I 
 KN> eventually went with the tcpexit.cmd design. 

It was not TCP/IP that was affected is was Peer Services. Somewhere during Warp
4 Fixpak development the startup of File and Printer sharing was broken, and
existing SHARES would not always startup correctly. Around that time I altered
the startup of my BBS machine to resolve all these issues, and also provide me
with a way of "controlling" the startup sequence should I NOT want things to
start up "normally". Its been running like this ever since (I think it was
around 1995 that I introduced the following).

The only entries in my BBS machine STARTUP Folder are -
  1. Pulse
  2. Memsize (System Resources monitor)
These 2 items always load. Everything else was removed from there and is keyed
off STARTUP.CMD.

My STARTUP.CMD contains the following -
  1. Call KeepLog.Cmd. This is a .CMD file that "rotates" any EXISTING LOG
files. This ensures I dont lose any useful log files. Its safe to re-run
because there is nothing to "rotate" if a new "target" file does not exist. IE
it does "If Exist xxx.LOG then Cycle xxx.LOG nn", where CYCLE deletes xxx.000,
renames xxx.?01 to xxx.?00, etc up to the last nn xxx.log files. The last LOG
file is xxx.?05 if nn = 5.
  2. Call TCPSTART.CMD. <== Fire up TCP/IP here.
     *** The next 4 items need TCP/IP to be up and running, however
TCPSTART.CMD wont return until it ends, so I dont really need to use
TCPEXIT.CMD.
  3. Starts a Syslog Daemon. 
  4. Starts a CRON.
  5. Starts a Time Server (NTP, SNTP, TIME and DAYTIME).
  6. Starts a Web Server (Apache).
  7. Calls SREXX.CMD. This is a simple but CRITICAL script that pre-loads all
REXX DLL's that I might need (I use a fair bit of Rexx for BBS stuff). It also
runs a VERY important Rexx function, SySWaitForShell(). This is a NON-PM Rexx
function that simply runs and WAITS, and does NOT terminate until the Work
Place Shell is up and fully OPERATING! So NOTHING will process past this point
until the WPS is running. This is how I syncrhonise STARTUP.CMD to the WPS
startup.
  8. Sleep 5. This is a simple program that just sleeps for a further nn
seconds then terminates. This ensures that all the previous startups have time
to get going before it continues. Its also critical to have things like SYSLOGD
running as BIND runs "detached" so its output is not visible except via the
SyslogD File.
  9. Starts a local cacheing DNS Server (BIND). 
 10. Starts up Peer Networking by LOGGING IN A DEFAULT USER! I actually think
this resolves the SHARING startup issues experienced by Peer during W4 Fixpak
developement because doing it this way I have NEVER seen the sharing issues
under Warp 4 (I went W4, +FP6, +FP12, +FP15). The BBS machine has ALWAYS shared
4 drives to the local LAN and having a user logged in from the start has always
had SHARES work for me. 
 11. Sleep 10. This just gives me time to STOP anything else from starting if I
do NOT want the BBS to start up.
 12. Calls STARTUP2.CMD.

And STARTUP2.CMD contains -
  1. A small list of housekeeping stuff for BinkleyTerm, BinkD and the BBS
(Maximus), such as removal of .BSY files...
  2. Call BBSSTART.CMD

And BBSSTAART.CMD just fires up all the BBS related stuff -
  - Binkelyterm Lines (I had 4 running at one point), 
  - BinkD, 
  - my background mail procesor task,
  - etc.

So EVERYTHING is sequenced by STARTUP.CMD. All this is run on a W4 FP15,
Celeron 700 with 64MB RAM (~16MB free) and 10GB HD.

Cheers...............pk.


--- Maximus/2 3.01
 * Origin: Another Good Point About OS/2 (3:772/1.10)