Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020 
<== Date ==> <== Thread ==>

Subject: RE: Channel access problem on cygwin IOC
From: "Mark Rivers" <rivers@cars.uchicago.edu>
To: "Jeff Hill" <johill@lanl.gov>, <tech-talk@aps.anl.gov>
Date: Fri, 30 Sep 2005 11:30:29 -0500
Jeff,

> Another possibly is that an IOC was connected before and was 
> restarted. 

What exactly do you mean by this?  The cygwin IOC has indeeed been
started and stopped many times.  However, I have exited all channel
access clients that are connected to that IOC, both on the local Windows
machine and on other machines.  Does this matter?

Here is some more information which may be of interest:

- When I was having the problem an SNL program running in that cygwin
IOC was able to connect to the PVs fine.  That is just a CA client,
right?
- Other CA clients on the Windows machine were not able to connect.
- Ohter CA clients on remote machines were not able to connect.
- Rebooting the Windows machine fixed the problem, at least for now.
- The problem kind of seems like running out of a resource, perhaps with
SO_RESUSEADDR as you suggested?

The reason I am using cygwin-x86 and not win32-x86-cygwin is that I do
need the cygwin libraries for asyn, not just the GNU compilers, as
discussed on tech-talk this morning.

One minor point is that cygwin is nice because I can set up soft links
under cygwin so that the same configure/RELEASE files in every
application work for Linux, vxWorks and cygwin.  That does not work for
win32-x86 since one needs to use Windows syntax for paths, not Unix
syntax.  cygwin also lets me install an ssh server on the Windows
machine so I can do EPICS development on the Windows machine remotely
with good performance, no need to be sitting in front of it.

Mark


Replies:
RE: Channel access problem on cygwin IOC Jeff Hill

Navigate by Date:
Prev: RE: Asyn build under win32 Jeff Hill
Next: RE: Channel access problem on cygwin IOC Jeff Hill
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020 
Navigate by Thread:
Prev: RE: Channel access problem on cygwin IOC Ernest L. Williams Jr.
Next: RE: Channel access problem on cygwin IOC Jeff Hill
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020 
ANJ, 02 Sep 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·