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

20021022: Setting up LDM for McIDAS-XCD (cont.)

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 20021022: Setting up LDM for McIDAS-XCD (cont.)
  • Date: Tue, 22 Oct 2002 14:35:20 -0600
>From: Richard Massa <address@hidden>
>Organization: UC Davis
>Keywords: 200210150109.g9F19F112387 McIDAS-XCD LDM

Richard,

>Sure... Primary group stuff has bit me before... I should have thought of
>that,

I should have suspected it sooner.

>though I suspect setting the sticky bit on /a/data/ldm/mcidas would work
>too...

Except that the problem is that the data monitors are seemingly not able
to create/update files in ~mcidas/workdata.

>I'll change the groups right now.

As soon as I saw your message, I recursively changed the group of all files in
~mcidas.  This worked for everything except:

~mcidas/mcupdate

which is owned by root.  While talking about mcupdate, I recommend that
you get rid of the following in ~mcidas:

mcupdate
mcunpack 
README
mcidasx2002.tar.Z
mcidas7.8
mcinet7.8.sh
src

The update procedure for Unidata McIDAS is to FTP the compressed update
tar file, mcupdate.tar.Z, into the ~/mcidas<ver>/update directory
and run the unpack script, mcunpack, from there.

OK, now the bad news.  Even though 'mcidas' and 'ldm' both have 'ldm'
as their primary group, the XCD data monitors are still not able to create/
update those data files in ~mcidas/workdata.  I really don't know what this
means at all!  Perhaps they both should be in only one account?  Perhaps
the machine needs a reboot?  I don't know why things are not working now.

Tom