Thanks to:
John Tan
alan_at_nabeth.cxo.dec.com
Dr. Thomas.Blinn_at_Compaq.com
It turns out to be a combination of "between the keyboard and chair" error
and an assumption made by a Digital coder.
Here's what I've learned:
1) The text displayed after login is contained in /etc/motd.
2) That file is modified at startup by the /sbin/init.d/motd script. The
purpose of the script is to check the first line of the /etc/motd and verify
that it matches the version string in the kernel. If it does not match it
replaces the version string in motd with the one from the running kernel.
The version string is the line that goes something like "Compaq Tru64 UNIX
V5.0A (Rev. 1094); Tue Mar 6 17:53:40 EST 2001".
Here's why I'm getting three lines of version strings:
1) The /sbin/init.d/motd script assumes that the first line contains the
version string AND that the version string begins with "Compaq Tru64 UNIX
V5.0A".
2) Since I type faster that I think I had neglected to specify single-user
mode when I booted with /genvmunix to rebuild the kernel. Since I booted
into multi-user mode with /genvmunix the /sbin/init.d/motd script got the
version string from /genvmunix whose version string is "Compaq Tru64 UNIX
P5.0A (Rev. 83); Wed Oct 4 07:25:43 EDT 2000". Notice that the beginning of
the string before the first parenthesis is different than the previous
version string.
3) Since the startup script assumes the version string begins with "Compaq
Tru64 UNIX V5.0A" and the version string with /genvmunix begins with "Compaq
Tru64 UNIX P5.0A" the script ended up prepending the /genvmunix version
string onto /etc/motd instead of replacing the old one. The same thing
happened in reverse when I booted off the new kernel thus I have 3 version
strings.
I was also asked why I'm rebuilding the kernel. I've been tasked with
setting up a warm-standy environment for our SAP production environment. SAP
has to be up in the remote site in under 4 hours. The short version of the
story is that I'm using EMC disks and their SRDF software to replicate all
disks, including boot, to the remote site on a regular basis. If I need to
failover then the servers at the remote site reboot using the EMC replicated
disks. Works pretty well except that the hardware in the remote site is
slightly different. The ES40 here has an itpsa controller and the remote one
has isp. I relinked the kernel to add the isp driver.
P.S. I still owe a summary to the list from a previous question regarding
the failover process. I apologize for the delay it will be posted shortly.
-----Original Message-----
From: Izzet Ergas [mailto:izzet.ergas_at_citrix.com]
Sent: Tuesday, March 06, 2001 6:08 PM
To: tru64-unix-managers_at_ornl.gov
Subject: login message changed after kernel relink
Does anyone know why the text when I log in changed from:
login: izzy
Password:
Last login: Tue Mar 6 14:26:55 EST 2001 from izzy.citrix.com
Compaq Tru64 UNIX V5.0A (Rev. 1094); Sun Feb 4 01:20:33 EST 2001
Tru64 UNIX Japanese Support V5.0A (rev. 831)
to:
login: izzy
Password:
Last login: Tue Mar 6 17:46:08 EST 2001 on console
Compaq Tru64 UNIX V5.0A (Rev. 1094); Tue Mar 6 17:53:40 EST 2001
Compaq Tru64 UNIX P5.0A (Rev. 83); Wed Oct 4 07:25:43 EDT 2000
Compaq Tru64 UNIX V5.0A (Rev. 1094); Sun Feb 4 01:20:33 EST 2001
Tru64 UNIX Japanese Support V5.0A (rev. 831)
The only change was a recompiled kernel. I'm curious about the two new lines
beginning with "Compaq Tru64...".
Thanks.
Received on Wed Mar 07 2001 - 00:48:13 NZDT