Nathan,
Bill Verity wrote:
> Interesting. My listkwd.file did not update either. Strange. I wonder what else didn't move over?
Two of us have now reported that the update was incomplete - at least
one important file was not updated.
Since you suggested that this might be a problem due to the common.tar.Z
file, I downloaded Linux-2.6.bin and ran it to repeat the upgrade. The
listkwd.file was not updated and the Configuration-owner keyword still
does not work.
I suspect that the problem is due to the fact that my listkwd.file from
14.3 has a date that is more recent than the file distributed with 14.4.
This is because I installed 14.3 so I could move files over from another
server that was running 14.3. Then I did the upgrade to 14.4. The
listkwd.file is dated 2005-09-01, the date I installed 14.3. This is, of
course, more recent than the 14.4 distribution file which is dated
2005-04-19.
I can easily copy over the listkwd.file, but I'm pretty sure there were
other files that were not updated. What is the best way to recover from
this situation?
I also need to know how to avoid this problem in the first place. I am
also LISTSERV maintainer for another site currently running LISTSERV for
Solaris 14.3. We will soon be moving to a Linux box and I was planning
to use the same process on it: install 14.3 on the Linux machine, copy
the lists to it, and then upgrade to 14.4. I have good reasons for not
wanting to upgrade the Solaris machine.
Thanks for your help.
--Dan
>
> At 3:34 PM -0400 9/6/05, Dan Wheeler wrote:
>
>>Nathan,
>>
>>Nathan Brindle wrote:
>>
>>>It sounds like your ~listserv/home/listkwd.file is out of date. How did you upgrade to 14.4? The new-fashioned .bin kit or the old-fashioned tar.Z kit?
>>>
>>>If the latter, it sounds like you didn't download and apply common.tar.Z along with Linux.tar.Z.
>>
>>Yes, I did it the old-fashioned tar.Z way.
>>
>>
>>>(I'm assuming this is for the KIDLINK site which is running Linux and not the UC site which is running Windows.)
>>
>>Yes, this is the Kidlink LISTSERV. We have both moved to a new machine and upgraded from 14.3 to 14.4. The new machine is a SuSE Enterprise Server 9 system with a 2.6 kernel. The old machine was a Debian system with a 2.4 kernel.
>>
>>I did a completely fresh install of 14.3 from the tar.Z's on our new machine. I then copied over all of our list and archive files from our old 14.3 installation. This went smoothly and both the lists themselves and the web archives worked smoothly.
>>
>>The next step was the upgrade to 14.4. I did unpacked the tar.Z's and did a make update. It is possible that I unpacked the wrong version of common.tar.Z but I don't think so. It seemed to work smoothly. The release command shows:
>>
>>LISTSERV(R) for unix version 14.4, managed by:
>> [log in to unmask]
>>
>>Master nodes file version: 2005-09-01 13:13:02 (VERS9922)
>>NJE peers file version: 2005-09-01 13:13:01
>>Internet peers file version: 2005-09-02 15:05:07
>>Service file version: 2005-09-01 13:13:01 (VERS9922)
>>Alias file version: 2005-09-01 13:13:01
>>Running under: Linux 2.6.5-7.191-default
>>Build date: 19 Jun 2005
>>
>>
>>I have just downloaded common.tar.Z again from:
>>
>>ftp://ftp.lsoft.com/LISTSERV/UNIX/
>>
>>The file information is:
>>
>>common.tar.Z 1663 KB 05/06/20 16:44:00
>>
>>When I untar this, I find:
>>
>>-rw------- 1 wheeledd wheeledd 153219 May 21 2002 listkeyw.memo
>>
>>but there is no listkwd.file in it!
>>
>>I have also looked in my temporary install directory for 14.4 and found this file:
>>
>>-rw------- 1 502 502 2653 2005-04-19 09:35 listkwd.file
>>
>>The temporary directory for 14.3 contains:
>>
>>-rw------- 1 15 users 2616 2004-11-30 21:38 listkwd.file
>>
>>This matches the file size for the file in my current 14.4 installation. My tentative diagnosis is that the make update failed to copy the new listkwd.file.
>>
>>What do you recommend that I do now? Is it enough to copy the listkwd.file to the right place or are there other things I should check?
>>
>>--Dan
>>
>>
>>
>>>At 11:16 AM 9/5/2005 -0400, Dan Wheeler wrote:
>>>
>>>
>>>>Hi,
>>>>
>>>>I was very pleased to read about the new Configuration-Owner keyword in version 14.4. This is exactly what we need. We have lots of moderators who should be able to change subscriptions but should NOT be messing around with the configuration.
>>>>
>>>>I upgraded our installation to 14.4 a few days ago and tried to set the Configuration-Owner for one of our lists. This is what I got:
>>>>
>>>>
>>>>>The following problems have been detected in the list header:
>>>>>
>>>>>* CONFIGURATION-OWNER= (KIDOWNZ)
>>>>>Warning: There is no keyword by that name - check the spelling.
>>>>
>>>>I know that this is a keyword that only the LISTSERV maintainer can change, but I am the LISTSERV maintainer.
>>>>
>>>>
>>>> Peace, Dan
>>>>
>>>>=> Daniel D. Wheeler - Education & Psychology, Univ. of Cincinnati
>>>>==> Email: [log in to unmask] URL: http://wheeler.uc.edu
>>>>===> Teaching Human Rights Online: http://oz.uc.edu/thro
>>>>====> KIDLINK: http://www.kidlink.org
>>
>>--
>> Peace, Dan
>>
>>=> Daniel D. Wheeler - Education & Psychology, Univ. of Cincinnati
>>==> Email: [log in to unmask] URL: http://wheeler.uc.edu
>>===> Teaching Human Rights Online: http://oz.uc.edu/thro
>>====> KIDLINK: http://www.kidlink.org
>
>
>
--
Peace, Dan
=> Daniel D. Wheeler - Education & Psychology, Univ. of Cincinnati
==> Email: [log in to unmask] URL: http://wheeler.uc.edu
===> Teaching Human Rights Online: http://oz.uc.edu/thro
====> KIDLINK: http://www.kidlink.org
|
