Re: 20010904: LDM startup, location of data

> ------- Forwarded Message
> 
> >To: Unidata Support <address@hidden>
> >From: "Patrick O'Reilly" <address@hidden>
> >Subject: LDM Configuration
> >Organization: UCAR/Unidata
> >Keywords: 200109042025.f84KOw102462
> 
> This is a multi-part message in MIME format.
> 
> ------=_NextPart_000_0093_01C13554.E4980EA0
> Content-Type: text/plain;
>         charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
> 
> Hello,
> 
> I have installed and started the LDM here on a Sun Sparc running Solaris =
> 8.  A couple questions.
> 
> In the LDM setup instructions, there is  a section "Start LDM at boot =
> time."  On such a system as I describe above, what is the most efficient =
> way to put this script into my system to get it to run as late as =
> possible at boot time?  Do I write the script into a file called =
> something like 'ldm.start' in /etc/init.d and then create symbolic links =
> from /etc/rc*.d directories?  I'm still a bit of a UNIX Admin novice! =20
> 
> Also, we have a UNIDATA feed group from papagayo.unl.edu.  Configuring =
> the pqact.conf file seems a little mysterious to me.  The decoders are =
> already included with the LDM, correct?  If I am configuring them for =
> GEMPAK and NWX, is it as simple as cutting the text from the downloaded =
> example files (nwx.tbl and decoders.tbl) that I grabbed from =
> http://www.unidata.ucar.edu/packages/gempak/GEMPAK5.6/configuration.html =
> and pasting it into my pqact.conf?
> 
> Thirdly, (sorry, better get it all out), I would like to put the =
> incoming data and decoded data in another place than the default =
> directory which seems to be /usr/local/ldm/data, I would like to use the =
> /space partition on my machine.  What files in the LDM would I need to =
> change to specify this? =20
> 
> Thank you for any help you can provide, this is my first LDM install =
> here!
> 
> Patrick=20
> 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Patrick O'Reilly                               Support Scientist
> The STORM Project            address@hidden
> 208 Latham Hall                             ph: 319-273-3789
> University of Northern Iowa
> Cedar Falls, IA 50614            =20
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~  =20
> 

Hi Patrick,

I'll answer your two LDM questions, and I believe Steve Chiswell will
answer your question about configuring pqact for GEMPAK.

Under Solaris, in order to invoke the LDM on system boot, you need to
put the script in the appropriate /etc/rcX.d directory and give it an
appropriate name. As an example, our Solaris box has rcS.d, rc1.d,
rc2.d, and rc3.d.  We've put the start script in rc3.d and named it
S95ldmd.   I won't go into this further as Solaris provides instructions
on how this all works, which are probably on your machine under
/etc/init.d/README.  However, for the sake of completeness, I will
include that text of that file at the end of this message.  If you still
have further questions about this please let me know.

Regarding putting data under /space, I would advise you to implement our
default setup and simply make a link from ~ldm/data to /space.  Assuming
you'd like a subdirectory under /space called ldm, in ~ldm you would do:
        mkdir /space/ldm        // make the ldm subdirectory 
        rm data                 // in case that directory or link already exists
        ln -s /space/ldm data   // make the link to /space/ldm and call it 
'data'

The default setup also calls for the logs directory to be a link to a
location under the data directory.  So also from ~ldm do:
        mkdir /space/ldm/logs
        rm logs
        ln -s /space/ldm/logs logs

I hope this helps.  Please let me know if you have more questions.

Anne
-- 
***************************************************
Anne Wilson                     UCAR Unidata Program            
address@hidden                  P.O. Box 3000
                                  Boulder, CO  80307
----------------------------------------------------
Unidata WWW server       http://www.unidata.ucar.edu/
****************************************************

/etc/init.d/README:

#ident  "@(#)README     1.8     93/03/01 SMI"   /* SVr4.0 1.4.1.1      
*/
Copyright (c) 1993, by Sun Microsystems, Inc.

This file describes the general mechanism for installing and executing
initialization and termination scripts used to implement init state
changes.

/etc/init.d contains initialization and termination scripts for
changing init states.  These scripts are linked when appropriate to
files in the rc?.d directories.

File names in rc?.d directories are of the form [SK]nn<init.d filename>
where 'S' means start this job, 'K' means kill this job, and 'nn' is
the relative sequence number for killing or starting the job.  When
entering a state (init S,0,2,3,etc.) the rc[S0-6] script executes those
scripts in /etc/rc[S0-6].d that are prefixed with 'K' followed by those
scripts prefixed with 'S'.  When executing each script in one of the
/etc/rc[S0-6] directories, the /sbin/rc[S0-6] script passes a single
argument.  It passes the argument 'stop' for scripts prefixed with 'K'
and the argument 'start' for scripts prefixed with 'S'.  There is no
harm
in applying the same sequence number to multiple scripts.  In this case
the order of execution is deterministic but unspecified.

Guidelines for selecting sequence numbers are provided in README files
located in the directory associated with that target state (i.e.:
/etc/rc[S0-6].d/README).

EXAMPLE:
        When changing to init state 2 (multi-user mode, network
resources
        not exported), /sbin/rc2 is initiated by the init process. The
        following steps are performed by /sbin/rc2.

        1. In the directory /etc/rc2.d are files used to stop processes 
        that should not be running in state 2.  The filenames are
prefixed
        with 'K'.  Each 'K'  file in the directory is executed (by
/sbin/rc2)
        in alpha-numeric order when the system enters init state 2. 
(see
        example under next item).

        2. Also in the rc2.d directory are files used to start processes
        that should be running in state 2.  As in the step above, each
'S'
        file is executed.

        Example:

                Assume the file /etc/netdaemon is a script that will
                initiate networking daemons when given the argument
                'start', and will terminate the daemons if given the
                argument 'stop'.  It is linked to
/etc/rc2.d/S68netdaemon,
                and to /etc/rc0.d/K67netdaemon.  The file is executed by 
                '/etc/rc2.d/S68netdaemon start' when init state 2 is
                entered and by '/etc/rc0.d/S67netdaemon stop' when
shutting
                the system down.

NOTE:

/sbin/rc2 has references to the obsolescent 'rc.d' directory.  These
references are for compatibility with old INSTALL scripts. New INSTALL
scripts should use the init.d directory for related executables.  The
same is true for the shutdown.d directory.