Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.eso.org/projects/dfs/team/more-about-CCSLite.txt Дата изменения: Tue Feb 13 19:33:04 2001 Дата индексирования: Sun Apr 13 22:53:41 2008 Кодировка: Поисковые слова: ngc 4736

SOME NOTES ABOUT HOW TO DEAL WITH CCSLITE ENVIRONMENT

For the majority of the following commands, the environment varilable RTAPENV
must be set to the name of the environment.

To verify that the environment is running:
low level:
ps -ef | grep ccs
you should see at least two processes:

vltmgr 28750 1 0 May 10 ? 0:00 ccsSHManager -s 20000
vltmgr 28744 1 0 May 10 ? 9:09 ccsScheduler -e wu0ohqs

though others may also be there.

*Note: the environment name used to be the hostname with the suffix 'qs'. This
convention has changed recently and often the environment names coincide with
the hostname.

*Note: on the VLT Control Model (DMD side), the user which runs the
environment is sometimes not the same one which is used at PSO (normally
vltmgr).

To check that the environment can communicate with another environment on the
LAN (to be checked for instance, if the communication OHS-BOB does not work)
msgSend msgServer PING ""

If everything works fine, you should get:
MESSAGEBUFFER:
OK

In any other case, one has to investigate the installation of the environment
(also at system level in /etc/services) under $VLTDATA.

To start the CCSLite environment:
Log in as vltmgr, set RTAPENV to wu0oh and issue:
vccEnvStart -e
eg vccEnvStart -e wu0oh

To stop the CCSLite environment
Log in as the user running the environment and issue:
vccEnvStop -e

GUI to start/stop/check/initialize environments:
It is advisable to use this GUI each time there are problems with
the environment, or it needs to be recreated or re-initialized.
In case of wrong installation it is often advisable to delete and
recreate the environment info in $VLTDATA.

The GUI can be started with:
vccEnv (preconditions are DISPLAY and RTAPENV set correctly)

select the environment name you need from the list and click to apply.
Now all actions like start/stop/check will take place on that
environment.


SUMMARIZE:
1/ login as vltmgr
2/ setenv RTAPENV and DISPLAY
3/ vccEnv
4/ 'environment' field as $RTAPENV, 'type' filed as QSEMU
5/ follow the loop: create, init, start, stop, delete, create, ...