EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

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  <20202021  2022  2023  2024  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  <20202021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: [EXTERNAL] vxW shell related
From: "Johnson, Andrew N. via Tech-talk" <tech-talk at aps.anl.gov>
To: Stefen Paul <stefen4114 at gmail.com>
Cc: EPICS tech-talk <tech-talk at aps.anl.gov>
Date: Wed, 11 Mar 2020 20:50:53 +0000
On Mar 11, 2020, at 10:38 AM, Hartman, Steven M. via Tech-talk <tech-talk at aps.anl.gov> wrote:
> 
>> On Mar 11, 2020, at 9:54 AM, Stefen Paul via Tech-talk <tech-talk at aps.anl.gov> wrote:
>> 
>> I am using vxWorks on MVME CPU boards. I have two queries related to the same :
> 
> You didn’t say which version of VxWorks you are using (and my experience may be out of date) but . . .

I agree that would definitely be helpful...


>> I want the shell to be accessible only through Telnet login and not through the default serial port terminal ... can it be done ?
> 
> I don’t think so. Traditionally VxWorks has required all targets to have a serial port terminal. 

Actually it might be possible, depending on whether the port is going to be used for something else or not. If you just don’t want people to be able to type commands through it one the OS is running I think that’s possible.

If you want to use it for I/O and to prevent VxWorks from ever sending or receiving console messages through it even at boot-up though, that would require rebuilding your boot rom and working out how you’d configure and boot the CPU. I’m sure you could build a VxWorks image that doesn’t connect its console up to the serial port, but you can’t run a telnet daemon in the boot-rom, and even if you could your session would die as soon as the newly booted OS initializes its network.

We actually do something vaguely similar but in reverse here; we build telnet into some of our VxWorks 6.9 OS images but we disable the telnet daemon task “ipcom_telnetd" by default, so someone has to connect via the console and enable the telnet task to be able to connect over the network. Telnet is much faster than going over a 9600 Baud serial port, but we aren’t allowed to keep the telnet ports open on our IOCs when we aren’t using them. We also configure the VxWorks telnet server to only accept at most one connection.

HTH,

- Andrew

-- 
Complexity comes for free, simplicity you have to work for.


Replies:
Re: [EXTERNAL] vxW shell related Stefen Paul via Tech-talk
References:
vxW shell related Stefen Paul via Tech-talk
Re: [EXTERNAL] vxW shell related Hartman, Steven M. via Tech-talk

Navigate by Date:
Prev: Re: [EXTERNAL] vxW shell related Hartman, Steven M. via Tech-talk
Next: Re: Real-time IOC and systemd Konrad, Martin via Tech-talk
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  <20202021  2022  2023  2024 
Navigate by Thread:
Prev: Re: [EXTERNAL] vxW shell related Hartman, Steven M. via Tech-talk
Next: Re: [EXTERNAL] vxW shell related Stefen Paul via Tech-talk
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  <20202021  2022  2023  2024 
ANJ, 13 Mar 2020 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·