[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[McIDAS #DPX-653014]: The mcenv command

Hi Francisco,

> I have a problem that is I am preparing to upgrade an installation of McIDAS-X
> and re-design a the webpage it runs on, but on my dummy test server with
> Lucid mcenv exits with no error:
> address@hidden:~$ mcenv
> address@hidden:~$

The McIDAS server command 'mcenv' does a number of things when it runs: create
shared memory that McIDAS commands will use; setup some McIDAS environment
variable values; and creates a new shell.  It is not surprising that you
don't see anything after running 'mcenv', but we need to make sure that the
'mcenv' you are running is the one in McIDAS.  Please do the following
and report the results back:

<login as 'mcidas'>
which mcenv

This will tell us which 'mcenv' is running (other packages might have an
executable also named 'mcenv').  If the copy of 'mcenv' that would be run
is not the one from McIDAS, you will need to adjust your PATH to make sure
that the directory in which the McIDAS executables are stored is first
in the PATH.

If the McIDAS version of 'mcenv' is the one that is run, please do the 

which mcenv

The 'env' will list out the value of all environment variables.  Since the 
'mcenv' will modify the environment variable MCPATH to add the ~/.mctmp/<shared 
memory id>
directory to the end, we should see if it is working by examining its value
after running 'mcenv'.

By the way, I am not sure what you mean by your reference to 'Lucid'.  Can you 
this further?


Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
Unidata HomePage                       http://www.unidata.ucar.edu

Ticket Details
Ticket ID: DPX-653014
Department: Support McIDAS
Priority: Normal
Status: Closed

NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.