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

[McIDAS #GHE-647300]: McIDAS-X 2016 isn't working because...



Hi Gilbert,

A couple of questions regarding the inability of McIDAS to "write"
to :0

- were you trying to run McIDAS as user 'sebenste' or 'mcidas'?

- if you were trying to run McIDAS as 'mcidas', did you login to
  the console as 'mcidas' or did you login in as 'sebenste' and
  then become 'mcidas'?

  If you logged into the console as 'mcidas', you would _own_ :0,
  so you would not run into problems trying to write to it.

- assuming that you logged into the console as 'sebenste' and then
  became 'mcidas', _how_ did you become 'mcidas'?

  The answer could be one of the following:

  - su mcidas

  - su - mcidas

  - ssh mcidas@<hostname>

  - some other way?

I am running CentOS 6.8 on my Unidata workstation, and I logon the console
as user 'yoksas'.  I become user 'mcidas' by doing a 'su - mcidas', and I
can run McIDAS with no problems.

Cheers,

Tom
--
****************************************************************************
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: GHE-647300
Department: Support McIDAS
Priority: Normal
Status: Open
===================
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.



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.