Gonna have to remember that '==' is not the same as '!=' all the time.
After a quick revision, I'm closer to operation. I can now get the data through the net from the NetBSD machine to the Linux machine if I do
"EPICS_CA_ADDR_LIST=10.145.5.38 ./camonitor fred".
I can start the example program or the excas program on the NetBSD machine, and do
"EPICS_CA_ADDR_LIST=10.145.5.38 ./StripTool" on the Linux machine and see the data now. It's getting better! Is it normal to have to specify the addresses in a list like that, or will the problem go away when I move the NetBSD machine inside our firewall?
I have a version of StripTool, alh, medm, and probe that all seem to work OK on the NetBSD machine, but right now I can't access data on the Linux machine because the NetBSD machine is currently connected outside the firewall that protects the Linux machine. I'll move the NetBSD machine inside the firewall tomorrow and do more testing.
I rewrote the osdNetIntf.c module, using the "getifaddr" call to step through the data list. Made the thing very short and simple.
Going to have to get serious about cleaning up what I've done to make it work, and figure some kind of testing for it.
*----------------------------------------
OK, that tells me what I needed to know.
When I run the excas program on the netBSD machine, I get a message saying the server isn't attched to a network. Looks like I haven't got the dependent code quite right. I'll correct it now that I know what doesn't work.
Thanks for the info.
David Dudley
>>> Kay-Uwe Kasemir <[email protected]> 08/31/06 2:51 PM >>>
Hi:
So you built EPICS base on a Linux machine and NetBSD?
Then you can test some things before you get into striptool etc.
EPICS base comes with a 'excas', 'cainfo' and 'camonitor'
commandline program.
Run excas on one machine.
While it's running, type
camonitor fred
You should see values.
Try the same on the other machine. Same result.
Now try 'excas' on one, 'camonitor fred' on the other.
Doesn't work?
Are they on the same subnet?
If not, try
EPICS_CA_ADDR_LIST=<ip of the machine that runs excas> camonitor
fred
Still doesn't work?
Ask Jeff Hill, [email protected].
-Kay
On Aug 31, 2006, at 15:41 , David Dudley wrote:
> Well, I'm moving along on the port (rather slowly at times...)
>
> I now have the base, alh, StripTool, medm, and probe built and I'm
> beginning to see if I can do anything with them.
>
> EDM is going to take a little longer, so I want to get as much
> operational as I can, as it doesn't make sense to spend a lot of
> time on things, if something basic isn't working.
>
> I built the example program (and the caClient program), and they
> both seem to work fine.
>
> Now, how do I access a data point on that machine from another
> one? I also have everything built on a Linux box that is beside me
> so I have something to compare to.
>
> Here's what I want to do: Start the example program on one
> machine, start StripTool or medm on the other, and access the info
> from that machine. Problem is, how do I enter the channel name?
> The only way I seem to get data is if I'm accessing the data on the
> local machine.
>
> David Dudley
>
> <David Dudley.vcf>
BEGIN:VCARD
VERSION:2.1
X-GWTYPE:USER
FN:David Dudley
TEL;WORK:880-3740
ORG:;MIS
TEL;PREF;FAX:880-3741
EMAIL;WORK;PREF;NGW:[email protected]
N:Dudley;David
END:VCARD
- Replies:
- Re: NetBSD Port Andrew Johnson
- Navigate by Date:
- Prev:
RE: NetBSD Port Jeff Hill
- Next:
Re: NetBSD Port Andrew Johnson
- 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: NetBSD Port Jeff Hill
- Next:
Re: NetBSD Port Andrew Johnson
- 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
|