Joachim,
I have run many instances of the same runtime image, on AIX servers,
over the years. My solution was to create a separate file directory for
each instance that I wanted to run. I then gave each image a unique
name, (this way I could differentiate them from each other when I grep'd
them). I wrote STOP, START, BOUNCE, STOPALL, STARTALL, and BOUNCEALL
shell scripts that allowed me to manage the starting and stopping of
images. One had to "cd" into each runtime directory to stop individual
image. But, the "ALL" scripts could be executed from any dirctory.
Each running image opened a maintenance TCP port that allowed shell
scripts to send commands to it. When stopping an image, the "stop" shell
script would send a shutdown command, via the maintenance TCP port, to
the running image. The shell script would then go into a wait loop, for
several seconds, waiting for the image to shut itself down. If the image
didn't, then the shell script would execute a kill -9 on the image.
Since I located each runtime in a separate directory, I was able to
grep/awk for the PID inside my "stop" shell scripts.
To keep all of my runtime images in sync, I kept the original runtime
image in a parent "source" directory. When a "start" shell script was
executed, it automatically copied the "source" image down into the
"runtime" directory, re-named the original to the name stored in the
directory and then started the image.
--
Brad Selfridge
913-829-6980
> --
> You received this message because you are subscribed to the Google
> Groups "VA Smalltalk" group.
> To view this discussion on the web visit
>
https://groups.google.com/d/msg/va-smalltalk/-/EkD_q0A-GMkJ.
> To post to this group, send email to
va-sma...@googlegroups.com.
> To unsubscribe from this group, send email to
>
va-smalltalk...@googlegroups.com.
> For more options, visit this group at
>
http://groups.google.com/group/va-smalltalk?hl=en.