EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  <19981999  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  Index 1994  1995  1996  1997  <19981999  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 
<== Date ==> <== Thread ==>

Subject: Re: Problem booting ioc w/ rsh instead of ftp
From: [email protected] (Ralph Lange)
To: [email protected], [email protected]
Date: Fri, 8 May 1998 11:34:46 +0200 (METDST)
John,

> I am trying to get an IOC to bootup using w/ rsh instead of ftp.

Why?  After booting the vxWorks image, the only disk access that deserves
to be called fast is NFS.

> When I make the switch I get the following messages (followed by the
> vxWorks Logo) and some other messages.  Can anyone determine from this
> why the IOC loads using ftp and not rsh?

(I assume you're using vxWorks 5.2 for the following ... I don't know if
Tornado works differently.)

> Attaching network interface ei0... done.
> 
> Attaching network interface lo0... done.
> 
> Loading... 437992 + 50684 + 27258
> 
> Starting at 0x1000...

This is getting and starting the vxWorks image. How this is done depends on
the flags and ftp password settings in the IOC's nvram. You may use
bootp/tftp, ftp, rsh access.

> Attaching network interface ei0... done.
> 
> Attaching network interface lo0... done.
> 
> Loading symbol table from apis:epicsApps/bin/mv167/vxWorks.sym
> ...apis:stty: : I
> nvalid argument

This is getting the symbol table. Note: The symbol table ist _ALWAYS_
loaded via rsh access, no matter which way the binary is loaded.

It seems that while opening the rsh to apis one of the the shell init
scripts (~/.cshrc ~/.zshenv ~/.profile /etc/cshrc /etc/profile ...) leads
to an error before the shell can execute what the IOC wants it to:
("cat epicsApps/bin/mv167/vxWorks.sym" in this case).
The shell is determined by the /etc/passwd (or NIS) entry of the user name
the IOC uses for the rsh (this user name is taken from the nvram).

In this case there is a "stty <something>" command in one of the init
scripts, where <something> is illegal (if you ask the shell).

> Error opening apis:epicsApps/bin/mv167/vxWorks.sym: status = 0x290010

This is just the message that getting the symbol table failed. I never saw
any explanation of the error codes in the doc. Four out of five Wind River
people don't know them, either.

Hope this helps,
Ralph

Replies:
Re: Problem booting ioc w/ rsh instead of ftp Andrew Johnson
References:
Problem booting ioc w/ rsh instead of ftp Hammonds, John

Navigate by Date:
Prev: Problem booting ioc w/ rsh instead of ftp Hammonds, John
Next: Re: Problem booting ioc w/ rsh instead of ftp Andrew Johnson
Index: 1994  1995  1996  1997  <19981999  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: Problem booting ioc w/ rsh instead of ftp Hammonds, John
Next: Re: Problem booting ioc w/ rsh instead of ftp Andrew Johnson
Index: 1994  1995  1996  1997  <19981999  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 
ANJ, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·