> One can only assume that the boot ROM code is correctly written so that it shuts down
> (closes) its TCP boot connection before jumping into the newly loaded system image.
> Therefore I don't fully understand why this problem occurs most frequently when the symbol
> table is loaded. Perhaps the problem is that they don't wait long enough for the boot
> TCP connection to fully shutdown the TCP state machine before jumping into the newly
> loaded system image. Frequently TCP connections linger briefly while the TCP disconnect
> sequence is completing after the socket "close()" call has already returned.
>
> Jeff
I posted on this problem a while back. For us the problem (60 seconds to load
symbol table) happens when booting with FTP on the MVME162, but not with the
MVME167. Changing to booting with rsh mostly fixes the problem. Now there
is only trouble when we reboot again quickly. On the second boot it will
still wait before it can load the symbol table.
Booting with rsh rather than ftp is also better from a security point of view,
no clear-text passwords on the network. You need to make a .rhosts file in
the home directory of that account. Make it an account with an invalid
password so no one can log in to it, and make the .rhosts file only have
entries for your IOCs and for the single account on those IOCs.
Mark Rivers
- Navigate by Date:
- Prev:
RE: Slow booting ioc Jeff Hill
- Next:
RE: Slow booting ioc Garrett D. Rinehart
- Index:
1994
1995
1996
1997
1998
<1999>
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
RE: Slow booting ioc Jeff Hill
- Next:
RE: Slow booting ioc Garrett D. Rinehart
- Index:
1994
1995
1996
1997
1998
<1999>
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|