[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 20011205: ldmd.conf multiple request line syntax



Hi Patrick, 

Nope, it is your OS that will be trying to make sense of the reg
expressions...some try to combine them, and some try without much luck.

>Would the whole thing go in between the quotes:  request HDS
> "string|string|string|string" or would it be like:

Yes, just one set of quotes.

Never too many questions......

Hope all is well in Iowa.


Keep me posted as to your success with this change.

Thank you,

-Jeff
____________________________                  _____________________
Jeff Weber                                    address@hidden
Unidata Support                               PH:303-497-8676 
NWS-COMET Case Study Library                  FX:303-497-8690
University Corp for Atmospheric Research      3300 Mitchell Ln
http://www.unidata.ucar.edu/staff/jweber      Boulder,Co 80307-3000
________________________________________      ______________________

On Wed, 5 Dec 2001, Patrick O'Reilly wrote:

> Hi Jeff,
> 
> I'm running Solaris 8....Would it also matter what OS stokes is running?  I
> will try the multiple strings on one line, it should be less than 256
> characters.  Would the whole thing go in between the quotes:  request HDS
> "string|string|string|string" or would it be like: request HDS
> "string"|"string"|"string"|"string" ?  And yes I got the pattern matches for
> the particular models from the pqact.conf examples.
> 
> Do I ask too many questions?  Making sure you're busy, thats all.
> 
> Patrick
> 
> ----- Original Message -----
> From: "Jeff Weber" <address@hidden>
> To: "Patrick O'Reilly" <address@hidden>
> Cc: "ldm-support" <address@hidden>
> Sent: Wednesday, December 05, 2001 2:52 PM
> Subject: Re: 20011205: ldmd.conf multiple request line syntax
> 
> 
> > Hi Patrick,
> >
> > What OS are you running?
> >
> > Some do not enjoy the multiple requests for the same feed from the same
> > machine. And if it does act on it, it is not done in a timely fashion, so
> > it would be wise to change to one line if possible
> >
> > It would be better if you could place them all in one line with | (or)
> > seperators..but you cannot exceed 256 characters.
> >
> > I bet you have already visited:
> > http://www.unidata.ucar.edu/packages/gempak/tutorial/pqact/decoders.tbl
> >
> > for pqact examples and help regarding pattern matching for ldmd.conf
> >
> > I began attempting to condense your reg expression, but I think the |
> > approach will be much simpler if not too long...
> >
> >
> > Hope this helps,
> >
> > If not let me know...
> >
> > Thanks,
> >
> > -Jeff
> > ____________________________                  _____________________
> > Jeff Weber                                    address@hidden
> > Unidata Support                               PH:303-497-8676
> > NWS-COMET Case Study Library                  FX:303-497-8690
> > University Corp for Atmospheric Research      3300 Mitchell Ln
> > http://www.unidata.ucar.edu/staff/jweber      Boulder,Co 80307-3000
> > ________________________________________      ______________________
> >
> > On Wed, 5 Dec 2001, Unidata Support wrote:
> >
> > >
> > > ------- Forwarded Message
> > >
> > > >From: "Patrick O'Reilly" <address@hidden>
> > > >Subject: ldmd.conf request line syntax
> > > >Organization: UNI
> > > >Keywords: 200112051940.fB5JerN13846 LDM ldmd.conf syntax
> > >
> > > This is a multi-part message in MIME format.
> > >
> > > ------=_NextPart_000_0031_01C17D92.ADE46C10
> > > Content-Type: multipart/alternative;
> > > boundary="----=_NextPart_001_0032_01C17D92.ADE77950"
> > >
> > >
> > > ------=_NextPart_001_0032_01C17D92.ADE77950
> > > Content-Type: text/plain;
> > > charset="iso-8859-1"
> > > Content-Transfer-Encoding: quoted-printable
> > >
> > > Hello all,
> > >
> > > I have been unsuccessfully trying to edit the request lines in ldmd.conf
> =
> > > to request only certain model data.  I used the text string expressions
> =
> > > from pqact.conf for each model.  I am trying to request eta212, eta215,
> =
> > > ngm211, avn211, mrf201, and ruc211.  I have attached (hopefully) my =
> > > ldmd.conf and ldmd.log from my try.  The ldm started okay, and the =
> > > ldmd.log looks okay, but no data came in for a while.  Does this =
> > > ldmd.conf look okay as far as syntax, or is this too many request lines?
> =
> > >  Thanks in advance, once again!
> > >
> > > Patrick
> > >
> > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > > Patrick O'Reilly                               Support Scientist
> > > The STORM Project            address@hidden
> > > 208 Latham Hall                             ph: 319-273-3789
> > > University of Northern Iowa
> > > Cedar Falls, IA 50614            =20
> > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~  =20
> > >
> > >
> > > ------=_NextPart_001_0032_01C17D92.ADE77950
> > > Content-Type: text/html;
> > > charset="iso-8859-1"
> > > Content-Transfer-Encoding: quoted-printable
> > >
> > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
> > > <HTML><HEAD>
> > > <META http-equiv=3DContent-Type content=3D"text/html; =
> > > charset=3Diso-8859-1">
> > > <META content=3D"MSHTML 5.50.4522.1800" name=3DGENERATOR>
> > > <STYLE></STYLE>
> > > </HEAD>
> > > <BODY bgColor=3D#ffffff>
> > > <DIV><FONT face=3D"MS Sans Serif" size=3D2>Hello all,</FONT></DIV>
> > > <DIV><FONT face=3D"MS Sans Serif" size=3D2></FONT>&nbsp;</DIV>
> > > <DIV><FONT face=3D"MS Sans Serif" size=3D2>I have been unsuccessfully =
> > > trying to edit=20
> > > the request lines in ldmd.conf to request&nbsp;only
> certain&nbsp;model=20
> > > data.&nbsp; I used the text string expressions&nbsp;from pqact.conf for
> =
> > > each=20
> > > model.&nbsp; I am trying to request eta212, eta215, ngm211, avn211, =
> > > mrf201, and=20
> > > ruc211.&nbsp; I have attached (hopefully) my ldmd.conf and ldmd.log from
> =
> > > my=20
> > > try.&nbsp; The ldm started okay, and the ldmd.log looks okay, but no =
> > > data came=20
> > > in for a while.&nbsp; Does this ldmd.conf look okay as far as syntax, or
> =
> > > is this=20
> > > too many request lines?&nbsp; Thanks in advance, once =
> > > again!</FONT></DIV>
> > > <DIV><FONT face=3D"MS Sans Serif" size=3D2></FONT>&nbsp;</DIV>
> > > <DIV><FONT face=3D"MS Sans Serif" size=3D2>Patrick</FONT></DIV>
> > > <DIV>&nbsp;</DIV>
> > > <DIV><FONT face=3D"MS Sans Serif"=20
> > > size=3D2>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<BR>Patrick=20
> > >
> O'Reilly&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
> > >
> ;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
> > > &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
> > > Support Scientist<BR>The STORM=20
> > >
> Project&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
> > >  <A=20
> > >
> href=3D"mailto:address@hidden";>address@hidden</A><BR>20=
> > > 8 Latham=20
> > >
> Hall&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
> > >
> sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
> > > p;&nbsp;&nbsp;&nbsp;&nbsp;=20
> > > ph: 319-273-3789<BR>University of Northern Iowa<BR>Cedar Falls, IA=20
> > >
> 50614&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
> > > bsp;=20
> > > <BR>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~&nbsp;&nbsp;=20
> > > <BR></FONT></DIV></BODY></HTML>
> > >
> > > ------=_NextPart_001_0032_01C17D92.ADE77950--
> > >
> > > ------=_NextPart_000_0031_01C17D92.ADE46C10
> > > Content-Type: application/octet-stream;
> > > name="ldmd.log.1"
> > > Content-Transfer-Encoding: quoted-printable
> > > Content-Disposition: attachment;
> > > filename="ldmd.log.1"
> > >
> > > Dec 05 19:23:52 blizzard rpc.ldmd[3940]: Starting Up (built: Aug 25 2000
> =
> > > 09:28:27)=0A=
> > > Dec 05 19:23:52 blizzard pqact[3942]: Starting Up=0A=
> > > Dec 05 19:23:52 blizzard stokes[3944]: run_requester: Starting Up: =
> > > stokes.metr.ou.edu=0A=
> > > Dec 05 19:23:52 blizzard stokes[3944]: run_requester: 20011205182352.685
> =
> > > TS_ENDT {{HDS,  "^[YZ].[UR].*/mETA"},{HDS,  "^Y.A... KWBH"},{H=0A=
> > > Dec 05 19:23:52 blizzard pqbinstats[3941]: Starting Up (3940)=0A=
> > > Dec 05 19:23:53 blizzard stokes[3944]: FEEDME(stokes.metr.ou.edu):
> OK=0A=
> > > Dec 05 19:23:54 blizzard localhost[3983]: Connection from localhost=0A=
> > > Dec 05 19:23:54 blizzard localhost[3983]: Connection reset by peer=0A=
> > > Dec 05 19:23:54 blizzard localhost[3983]: Exiting=0A=
> > > =0A=
> > >
> > > ------=_NextPart_000_0031_01C17D92.ADE46C10
> > > Content-Type: application/octet-stream;
> > > name="ldmd.conf.copy"
> > > Content-Transfer-Encoding: quoted-printable
> > > Content-Disposition: attachment;
> > > filename="ldmd.conf.copy"
> > >
> > > #####=0A=
> > > # $Id: ldmd.conf,v 1.13 2000/07/05 22:25:05 russ Exp $=0A=
> > > # Sample ldmd.conf for ldm5=0A=
> > > ####=0A=
> > > #=0A=
> > > # This is the main configuration file for the LDM server. All lines that
> =
> > > start=0A=
> > > # with a "#" sign are comments.=0A=
> > > #=0A=
> > > # To debug an LDM that hangs on start up, run the following from LDM =
> > > home:=0A=
> > > # % bin/rpc.ldmd -vl - -q data/ldm.pq etc/ldmd.conf=0A=
> > > #=0A=
> > > # If the LDM still hangs, comment out all lines in this file except
> noted=0A=
> > > # allow line entry below, try again.=0A=
> > > #=0A=
> > >
> #########################################################################=
> > > ######=0A=
> > > # Exec Entries=0A=
> > >
> #########################################################################=
> > > ######=0A=
> > > #=0A=
> > > # Programs that can share a queue with rpc.ldmd server, these
> programs=0A=
> > > # are started by the "exec" command and are in the same process
> group.=0A=
> > > #=0A=
> > > exec "pqbinstats"=0A=
> > > exec "pqact"=0A=
> > > exec "xcd_run MONITOR"=0A=
> > > #exec "pqsurf"=0A=
> > > #=0A=
> > >
> #########################################################################=
> > > ######=0A=
> > > # Request Entries=0A=
> > >
> #########################################################################=
> > > ######=0A=
> > > #=0A=
> > > # LDM5 servers request data from Data Sources=0A=
> > > #=0A=
> > > # request <feedset> <pattern> <hostname pattern>=0A=
> > > #=0A=
> > > #request WMO ".*" uni0.unidata.ucar.edu=0A=
> > > request HDS "^[YZ].[UR].*/mETA" stokes.metr.ou.edu=0A=
> > > request HDS "^Y.A... KWBH" stokes.metr.ou.edu=0A=
> > > request HDS "^[YZ].Q.*/mNGM" stokes.metr.ou.edu=0A=
> > > request HDS "^Y.Q... KWBC.*(/mAVN|/mSSIAVN)" stokes.metr.ou.edu=0A=
> > > request HDS "^[YZ].Q.*/mRUC" stokes.metr.ou.edu=0A=
> > > request NNEXRAD "/p...(ARX|DMX|DVN)" stokes.metr.ou.edu=0A=
> > > request NMC3 ".*" stokes.metr.ou.edu=0A=
> > > #=0A=
> > > #=0A=
> > >
> #########################################################################=
> > > ######=0A=
> > > # Allow Entries=0A=
> > >
> #########################################################################=
> > > ######=0A=
> > > #=0A=
> > > # Giving permission for a Data Sink to perform a request to your LDM=0A=
> > > #=0A=
> > > # allow <feedset> <hostname pattern>=0A=
> > > #=0A=
> > > # Giving permission to your own machine and Unidata=0A=
> > > #=0A=
> > > # Under no circumstances comment out the next allow entry to
> localhost=0A=
> > > # The LDM will NOT start if the lines are commented out.=0A=
> > > allow ANY=0A=
> > >     =
> > >
> ^((localhost|loopback)|(127\.0\.0\.1\.?$)|([a-z].*\.unidata\.ucar\.edu\.?=
> > > $))=0A=
> > > #=0A=
> > >
> #########################################################################=
> > > ######=0A=
> > > # Accept Entries=0A=
> > >
> #########################################################################=
> > > ######=0A=
> > > # ACCEPT: Who can feed us, currently this action is ONLY needed for WSI
> =
> > > data=0A=
> > > #=0A=
> > > # accept <feedset> <pattern> <hostname pattern>=0A=
> > > #=0A=
> > > # accept anything from yourself=0A=
> > > #=0A=
> > > #accept ANY ".*" ^((localhost|loopback)|(127\.0\.0\.1\.?$))=0A=
> > > #=0A=
> > > # accept from your upstream site=0A=
> > > #=0A=
> > > # WSI is using ldm4 protocol so the accept is still required=0A=
> > > #accept WSI=0A=
> > > #    .*=0A=
> > > #    ^[a-z].*\.uni\.wsicorp\.com$=0A=
> > > #=0A=
> > >
> #########################################################################=
> > > ######=0A=
> > > # End =0A=
> > >
> #########################################################################=
> > > ######=0A=
> > >
> > > ------=_NextPart_000_0031_01C17D92.ADE46C10--
> > >
> > >
> > > ------- End of Forwarded Message
> > >
> > >
> >
> 
>