After. Someone in our group ran into this problem last fall with a
device support to bridge to snmp, which apparently has really long
names.
Michael
> -----Original Message-----
> From: Steve Kinder [mailto:[email protected]]
> Sent: Monday, March 15, 2010 1:09 PM
> To: Davidsaver, Michael; Andrew Johnson
> Cc: [email protected]
> Subject: Re: INP field length
>
> Hi David
>
> No I don't actually see an error at the moment and things work. I
> really
> wanted to make sure I understood any limitations of this sort that
> exist and
> would limit the combined length of the DEVICE and port strings in my
> case.
> You seem to be saying that the INP string needs to be less than 80
> characters. Would that be before or after macro expansion? For now I
> don't
> think either cause me a problem with a limit of 80.
>
> Regards
>
> Steve
>
> ----- Original Message -----
> From: "Davidsaver, Michael" <[email protected]>
> To: "Andrew Johnson" <[email protected]>; "Steve Kinder"
> <[email protected]>
> Cc: <[email protected]>
> Sent: Monday, March 15, 2010 4:29 PM
> Subject: RE: INP field length
>
>
> Steve,
>
> One of the limitations on the length of INP or OUT is dbPutString in
> dbStaticLib.c (search for 'string[80]'). When you reach this limit
you
> will see the message "dbPutString received a string that is too long".
> Do you see this?
>
> Michael
>
> > -----Original Message-----
> > From: [email protected] [mailto:tech-talk-
> > [email protected]] On Behalf Of Andrew Johnson
> > Sent: Monday, March 15, 2010 12:12 PM
> > To: Steve Kinder
> > Cc: [email protected]
> > Subject: Re: INP field length
> >
> > Hi Steve,
> >
> > On Monday 15 March 2010 10:46:42 Steve Kinder wrote:
> > >
> > > Thanks for the reply, that was what I thought. But just to clarify
> my
> > > specific case. I'm using StreamDevice2 and have a INP field as
> > follows with
> > > template/substitution.
> > >
> > > field(INP, "@TEST.protocol getCs($(DEVICE),C2,C3,C4) $(port) 0")
> > >
> > > If I understand things correctly, whatever the length of DEVICE
and
> > port I
> > > shouldn't encounter problems. Well due to the length of the field
> at
> > least.
> >
> > I just checked something else and found a 1023 character length
limit
> > to each
> > input line before and after macro expansion in the parser, although
I
> > don't
> > think that will affect you.
> >
> > - Andrew
> > --
> > The best FOSS code is written to be read by other humans -- Harald
> > Welte
>
>
>
- References:
- INP field length Steve Kinder
- Re: INP field length Andrew Johnson
- Re: INP field length Steve Kinder
- Re: INP field length Andrew Johnson
- RE: INP field length Davidsaver, Michael
- Re: INP field length Steve Kinder
- Navigate by Date:
- Prev:
Re: INP field length Steve Kinder
- Next:
Re: ChannelArchiver on Solaris? Matthias Clausen
- 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: INP field length Steve Kinder
- Next:
Re: INP field length 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
|