[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
20040930: Regarding LDM statistics to remote host
- Subject: 20040930: Regarding LDM statistics to remote host
- Date: Fri, 01 Oct 2004 11:12:44 -0600
Ramakrishna,
The rtstats data is sent to the remotehost using feedtype EXP
and pattern described in the rtstats.1 manpage. You will need
to add the ACCEPT entry for the EXP feedtype and rtstats pattern
on the machine that will receive the data. This is a standard LDM
program (similar to pqsend) using port 388.
A sample pqact.conf processing line is shown here:
http://gforge.unidata.ucar.edu/forum/forum.php?thread_id=16&forum_id=11
Steve Chiswell
Unidata User Support
>From: address@hidden
>Organization: UCAR/Unidata
>Keywords: 200409301744.i8UHivUE018621
>Hello support team,
>
> I am the software developer in Center for Analysis and Prediction of
> Storms, University of Oklahoma, Norman, OK. I am working on the IRaDS projec
> t as part of which I am developing some adhoc modules to be used along side t
> he LDM for our research institute. In this context I need some help regarding
> a small issue. It goes like this.
>
> in the LDMHOME/etc/ldmd.conf file if we have a line for starting rtsta
> ts, similar to,
>rtstats -h remotehost,
>the statistics will be delivered to the 'remotehost' identified by either IP a
> ddress or hostname. Now I want to utilize this feature to make the LDM runnin
> g on our client machine to our server in CAPS. But my question is how can I r
> eceive the statistics our server (remotehost)? Is there any module already in
> LDM? If not, onto what port/what file the statistics will be written and wha
> t server should we keep running on server and on what port?
>
>I will be grateful if you can help me out with this as if the solution already
> exists, it will save me lot of time.
>
>Thank you,
>Ramakrishna Pantangi
>Research Assistant
>IRaDS development team
>CAPS, University of Oklahoma,
>Norman, OK, USA
>
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publicly available
through the web. If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.