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

Re: 19990707: ldmadmin script

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: Re: 19990707: ldmadmin script
  • Date: Wed, 7 Jul 1999 10:40:32 -0600 (MDT)
Jim,

I was really think of eliminating the command restart. For some reason it
always had some problems. The users could do a stop then start with maybe
a sleep inbetween.  Let me think about it some more.l

Thanks,
Robb...



On Wed, 7 Jul 1999, Jim Cowie wrote:

> Robb Kambic wrote:
> > 
> > Jim,
> > 
> > Thanks for the observation.  The purpose of the ldmadmin_ps was to show
> > the users that the ldm was really stopped. I'll change the ldmadmin script
> > so the ldm.pid file is deleted correctly.  If you want, delete the added
> > line ldmadmin_ps
> > 
> 
> OK, I did that to get it going. Sounds like you'll still have to do some
> changes in the other functions to get "ldmadmin restart" to work though.
> The restart option does:
> 
> sub restart_ldm {
> 
>         stop_ldm();
>         start_ldm();
> }
> 
> stop_ldm() calls ldmadmin_ps(), and since it doesn't return from there,
> then start_ldm() never happens. Sounds like you need a function like
> ldmadmin_ps(), but one that doesn't exit upon error. Sumthin like
> that anyway.
> 
> -jim
> 

===============================================================================
Robb Kambic                                Unidata Program Center
Software Engineer III                      Univ. Corp for Atmospheric Research
address@hidden             WWW: http://www.unidata.ucar.edu/
===============================================================================