This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
>From: Steve Emmerson <address@hidden> >Organization: UCAR/Unidata >Keywords: 200506292117.j5TLHWjo001930 Hi Janet, This is a quick follow-up on the note that Steve sent earlier. re: > As the superuser (i.e., root): > > 1. Change the ownership of the hupsyslog(1) utility, > $HOME/bin/hupsyslog, to "root" and then enable the setuid > bit. This will enable proper rotation of the LDM logfiles. The HOWTO for changing ownership of rpc.ldmd and hupsyslog can be found in: Unidata HomePage http://www.unidata.ucar.edu LDM HomePage http://www.unidata.ucar.edu/content/software/ldm LDM 6.3.0 http://my.unidata.ucar.edu/content/software/ldm/ldm-6.3.0/index.html Installing, Configuring, and Activating the LDM System in the LDM Basics webpages http://my.unidata.ucar.edu/content/software/ldm/ldm-6.3.0/basics/index.html#installation Binary installation http://my.unidata.ucar.edu/content/software/ldm/ldm-6.3.0/basics/binary-install-steps.html On the last page, jump to the section that starts: Make rpc.ldmd and hupsyslog set-uid-root The procedure is: cd $HOME/$VDIR/bin <- e.g., cd ~ldm/ldm-6.3.0/bin su ... chown root rpc.ldmd hupsyslog chmod u+srwx,g+rx,o+rx rpc.ldmd hupsyslog Note that this step must be done as the superuser (i.e. root). Cheers, Tom >I did the following: > > 1. Commented-out the "exec pqbinstats" entry in the LDM > configuration-file, $HOME/etc/ldmd.conf, because it uses a lot > of the CPU for no good purpose. > > 2. Commented-out the "exec pqact" entry in the LDM > configuration-file, $HOME/etc/ldmd.conf, because you don't seem > to be doing anything with the data (the pqact(1) > configuration-file, $HOME/etc/pqact.conf, appears to be the > example one that comes with the distribution). > > 3. Added a crontab(1) entry to rotate the LDM logfile at midnight, > local time, every day. > > 4. Added the entry > > allow ANY ^[a-z].*\.atd\.ucar\.edu$ > > to the LDM configuration-file, $HOME/etc/ldmd.conf. This might > be too general for you and you might want to restrict it to, for > example > > allow ANY ^linus\.atd\.ucar\.edu$ > > An ALLOW entry like this has never been necessary -- that I can > recall. I don't know why your situation is different. > > 5. Restarted the LDM. The command > > ldmping > > now works, as do the various rpcinfo(1) commands such as > > rpcinfo -t linus 300029 6 > >You should > > As the superuser (i.e., root): > > 1. Change the ownership of the hupsyslog(1) utility, > $HOME/bin/hupsyslog, to "root" and then enable the setuid > bit. This will enable proper rotation of the LDM logfiles. > > 2. Add the line > > search atd.ucar.edu > > to the top of the file /etc/resolv.conf. It used to have > this. Why was it removed?) > > As the LDM user on another system, try to ldmping(1) the LDM on > Linus (I couldn't log onto Cirque). > >Regards, >Steve Emmerson > >------- Original Message > >Date: Wed, 29 Jun 2005 14:06:39 -0600 >From: Janet Scannell <address@hidden>To: Steve Emmerson <steve@unida > t > a.ucar.edu> >Subject: Re: Getting LDM on plane to receive via UCAR RAS and PPP > >Steve, > >The rcp.ldmd was not the right permissions, owner. I fixed that and now >rcpinfo shows port 388 for the ldm port on linus. (That's what happens >when you use someone else's install of ldm instead of reinstalling it >yourself.) > >rpcinfo -t linus 300029 6 from linus still does not work correctly. I've chec > k >ed the allow lines in the conf file and restarted ldm and still the same behav > i >or. > >The ldmping from an outside host now gives a different error: >ldmping linus.atd.ucar.edu >Jun 29 19:34:14 State Elapsed Port Remote_Host rpc_stat >Jun 29 19:34:14 ADDRESSED 0.014074 0 linus.atd.ucar.edu RPC: >Unable to receive; errno = Connection reset by peer > >which seems to be related to the rpcinfo command not working on linus. > >Sure, you are welcome to log onto linus and cirque. I think the main >problem now is just linus and not cirque. cirque is currently connected >to the internal network as cirque.atd.ucar.edu. > >Thanks, >Janet > > >------- End of Original Message Cheers, Tom -- +-----------------------------------------------------------------------------+ * Tom Yoksas UCAR Unidata Program * * (303) 497-8642 (last resort) P.O. Box 3000 * * address@hidden Boulder, CO 80307 * * Unidata WWW Service http://www.unidata.ucar.edu/* +-----------------------------------------------------------------------------+