20030508: McIDAS installation at UFRJ (cont.)

>From:  David Garrana Coelho <address@hidden>
>Organization:  UFRJ
>Keywords:  200305071213.h47CDk7U003082 McIDAS-X v2002b install

Hi David,

>       Just created the mcadde user, member of ldm group, same home
>directory of mcidas user.

Wonderful.  Thanks for the quick action!

>Not sure how to make this account not allow
>logins, may I lock the account?

The easiest way to do this is to set the login shell to something
that doesn't exist.  We recommend making it /bin/false.

>I also added mcidas user to ldm group (as
>secondary group), but kept him on his original group (mcidas) to not mess
>with files permissions on its home directory. Is it enough or should I
>really change his primary group to ldm group?

I think that this should be enough, but I will checke to make sure
by reverting permissions on ~ldm and ~ldm/data to group read/write/execute
and world read/execute.

>(and do recursive group
>change on its home directory?)

This may be necessary, but I will check on things first.

>I didn't make this because you are logged
>on account right now, dont want to trip acidentally on what you are
>doing...=)

Thanks for thinking of me!

>       You mentioned something about netcdf installation. Brisa haves
>netcdf installed under /usr/local/netcdf directory.

The netCDF is bundled with McIDAS (so that sites that havn't already
grabbed and built it don't have to), so I needed to set the environment
variables that would allow the build to proceed no matter what.

>       Lemme know if you need something else.

Will do, thanks.

>       Thanks once more.

No worries.

From: David Garrana Coelho <address@hidden>
Date: Thu, 8 May 2003 14:45:48 -0300 (BRT)

Tom,

>       Disregard last message about groups. Now ldm,mcidas and mcadde
>user are all in ldm group. Still not sure how to make mcadde not allow
>logins.

OK, great!  This is the recommended setup for these users.  Also, I
recommend that the umask for both 'mcidas' and 'ldm' be set to 002.
This is typically needed when McIDAS-XCD decoders are run since the
ownership/use of the output data files are shared between the two
users.  If you are not going to want to use McIDAS as a display
and analysis package, the changing of umask for 'ldm' will probably
not be necessary (I didn't check, so your 'ldm's umask may already
be 002).

Tom
--
+-----------------------------------------------------------------------------+
* Tom Yoksas                                             UCAR Unidata Program *
* (303) 497-8642 (last resort)                                  P.O. Box 3000 *
* address@hidden                                   Boulder, CO 80307 *
* Unidata WWW Service                             http://www.unidata.ucar.edu/*
+-----------------------------------------------------------------------------+