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

20050128: "sync" in ldmadmin stop

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: 20050128: "sync" in ldmadmin stop
  • Date: Sun, 30 Jan 2005 14:53:39 -0700
>From: Harry Edmon <address@hidden>
>Organization: University of Washington
>Keywords: 200501282148.j0SLmTv2010367 LDM ldmadmin sync

Hi Harry,

>Why is the "sync" in the ldmadmin stop script before the server goes 
>down?

We were just discussing the running of 'sync' in ldmadmin the other day,
so your inquiry is very timely.

>On my Linux box sith a 4GB cache, the sync takes a considerable 
>amount of time.  Wouldn't a sync after the server goes down make more sense?

I will let Steve E. comment on whether or not the sync could occur
after the signal was sent telling the lead rpc.ldmd to shutdown.

Cheers,

Tom
--
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.