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

19991222: NLDN change

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: 19991222: NLDN change
  • Date: Wed, 22 Dec 1999 11:36:44 -0700
>From: address@hidden
>Organization: University of Northern Iowa
>Keywords: 199912221723.KAA23061 LDM IDD NLDN

Alan,

>I'm attempting to make the pqact.conf change
>for NLDN, as per your email.  When I come to your step
>5 (the kill statement), it tells me "No such process".

Assuming that you are on the machine running the LDM and the LDM is, in
fact running, do the following after logging in as the user running the
LDM (typically 'ldm'):

ps -eaf | grep pqact

On our system running the LDM (Solaris x86), the ps command resulted in
the following output:

ps -eaf | grep pqact
     ldm   403   400  1   Dec 11 ?       144:29 pqact
     ldm 27808 15956  0 11:04:46 pts/4    0:00 grep pqact

From this listing, we can see that the process ID for 'pqact' is 403.
The kill -HUP invocation that needs to be run is, therefore:

kill -HUP 403

>Maybe I'm not giving it the correct process ID; I'm
>assuming the first number on the response to the ps
>command in your step 4 is the process ID.

It should be.  What does your 'ps' listing look like?  What is the
operating system that is running on your LDM machine (Don says that
findeisen is running Linux; what version is it)?

>Thanks for your help.

No problem.  We should be able to get this straightened out pretty
quickly so that you will not lose any NLDN data.  By the way, in case
you didn't notice David Knight's email to ldm-users a little while
back, Suny Albany will be shutting down their systems for a couple of
days starting December 31 (I believe).  The reason is for scheduled
network work, not Y2K things.  David will be "throwing the switch" upon
restart of the NLDN machine (striker) that changes the year format from
YY to CCYY.

>Merry Christmas and say hi to Don for me.

Same to you, and I will pass along your wishes to Don.

Tom