On Friday 21 September 2007 15:54, Eric Norum wrote:
> On Sep 21, 2007, at 8:36 AM, Benjamin Franksen wrote:
> > On Friday 21 September 2007 12:30, Benjamin Franksen wrote:
> >> I have not produced a fix for this problem. I guess you (Eric) know
> >> better how to approach this.
> >
> > Well, my current, very crude, solution is to replace all (seven)
> > clnt_destroy calls by
> >
> > if (pvxiPort->rpcClient) {
> > clnt_destroy(pvxiPort->rpcClient);
> > pvxiPort->rpcClient = 0;
> > } else {
> > if(pasynUser) asynPrint(pasynUser,ASYN_TRACE_ERROR,
> > "%s internal error: RPC handle already
> > destroyed\n",pvxiPort->portName);
> > }
>
> Would an alternative fix be to change all the clnt_destroy calls in
> vxiConnectPort to:
> @@ -933,7 +934,8 @@
> "%s vxiConnectPort neither system controller nor "
> "controller in charge -- initialization aborted
> \n",
> pvxiPort->portName);
> - clnt_destroy(pvxiPort->rpcClient);
> + if (pvxiPort->server.connected)
> + vxiDisconnectPort(pvxiPort);
> return asynError;
> }
> }
Looks reasonable. I'll try it.
Cheers
Ben
- References:
- Asyn/VXI-11 problems Benjamin Franksen
- Re: Asyn/VXI-11 problems Benjamin Franksen
- Re: Asyn/VXI-11 problems Eric Norum
- Navigate by Date:
- Prev:
Re: Asyn/VXI-11 problems Eric Norum
- Next:
Re: Asyn/VXI-11 problems Benjamin Franksen
- 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: Asyn/VXI-11 problems Benjamin Franksen
- Next:
Re: Asyn/VXI-11 problems Dirk Zimoch
- 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
|