LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Garrie Burr <[log in to unmask]>
Thu, 24 Aug 2000 16:54:20 -0500
text/plain (66 lines)
OK, TELL LISTSERV NODESGEN did the trick (after I beat a bruise into my
forehead for forgetting the difference between LISTSERV commands and CP
commands)... or at least it ran through some updates on the screen,
reindexing the PEERS tables.  The list owners have been notified to run
some tests so I guess we'll wait to see what happens now.

I'm wondering still about the timing of the whole thing...  but it still
sounds like we're not sure which file exactly is causing the problem,
whether it's one of the old December 99 PEERS files or the new BITEARN
NODES file or a combination of both.

I'll let you know, of course, the results of our testing here...

Thanks!











On Thu, 24 Aug 2000 15:27:16 -0500 you said:
>On Thu, 24 Aug 2000 13:48:32 -0500 I wrote:
>>NODESGEN is an unknown command on our VM Server and I've never had to
>
>And Nathan answered:
>
>>>That I don't understand.  Did you issue it and get an unknown command
>error?  It's been around for ages.  I see references to it clear back
>to 1.6d and the implication is that it existed before that.<<
>
>I get 'Unknown CP/CMS command.' when issuing it from the LISTSERV account.
>I'd already seen the command in the manual (wasn't sure what <WTONLY>
meant
>as a variable) but issuing the command separately or with a variable
causes
>the same 'Unknown CP/CMS command.' to appear.

It's not a CP/CMS command.  It has to be mailed to LISTSERV or issued
while LISTSERV is running in the console.  TELL LISTSERV NODESGEN would
probably work also.  WTONLY means "just rebuild the links weights tables"
and isn't germane at this point.

>It is indeed old WUVMD.WUSTL.EDU but I've had to download the files
>manually since I started watching over things several years ago.  This is
>the first time we've had a problem.  I've had the procedure stored in a
>file so I can just copy/paste the commands in without worrying about
typos.
>I assume it's been ftping as text since this is the first (possible)
>problem.

This is not good.  You should be getting updates from us.  I will check
with Eric.

>I notice that our INTPEERS and PEERS NAMES files are dated, respectively
>12/30/99 and 12/20/99.  These need updates, too??

Yes, they were just updated recently.  Again, let me check with Eric
to see why you aren't getting these automatically.

Nathan

ATOM RSS1 RSS2