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.
Jim, I don't have any suggestions now, but I plan to build the ldm on our BSD machine to get any insights. Will let you know the results. Robb... On Thu, 21 Jan 1999, Jim Koermer wrote: > Robb Kambic wrote: > > > > On Thu, 21 Jan 1999, Unidata Support wrote: > > > > > >To: address@hidden > > > >From: Jim Koermer <address@hidden> > > > >Subject: LDM-5.0.6 Problem > > > >Organization: . > > > >Keywords: 199901211542.IAA22899 > > > > > > I have just finished installing LDM-5.0.6 on a FreeBSD machine. I'm > > > feeding it with another of my machines. Data seems to be ingesting okay, > > > but I can't seem to generate an ldmd.log, no matter what I have tried. > > > Any ideas on what might be my problem? > > > > > > Jim > > > > Jim, > > > > There is no /etc/syslog.pid file on BSD, so one has to use the killall > > command. I would first test it from the command line aw user root. > > > > % /usr/bin/killall -HUP syslogd > > > > It seemed to work. At least, I didn't get any error messages. > > > If that works, then create a new hupsyslog in the bin directory by making > > a hupsyslog shell script. > > > > #! /bin/sh > > # > > # Script to send a SIGHUP to syslog(8), causing it to close and reopen > > # all log files. > > # NB: Must be run by root or the killall(1) will fail; > > # > > /usr/bin/killall -HUP syslogd || exit 1 > > > > Then execute these commands as root to make the correct permissions: > > > > % chmod 550 hupsyslog > > % chown root hupsyslog > > % chmod u+srwx,g+rwx,o+rx hupsyslog > > > > I did all of the above. > > > If syslogd doesn't get a HUP, then it doesn't know about the ldmd.log > > file. For sanity sake, you did edit syslog.conf and add local0.debug etc > > These items were done before my initial attempts. > > > and did a touch on the ldmd.log file. > > > > This was also done. > > Review at: > > http://www.unidata.ucar.edu/packages/ldm/ldmPreInstallList.html#s8 > > > > I followed this guidance line by line. > > Robb, > > I'm still getting no ldmd.log file, even though everything else seems to > be working okay. > > I did build LDM 5.0.3 on an older FreeBSD machine several years ago and > it has been working fine and building a log file without problem. I > tried cross checking each configuration item and still am not turning up > any clues. > > Jim > > Jim > -- > James P. Koermer E-Mail: address@hidden > Professor of Meteorology Office Phone: (603)535-2325 > Chair, Natural Science Department Office Fax: (603)535-2723 > Plymouth State College WWW: http://vortex.plymouth.edu/ > Plymouth, NH 03264 > =============================================================================== Robb Kambic Unidata Program Center Software Engineer III Univ. Corp for Atmospheric Research address@hidden WWW: http://www.unidata.ucar.edu/ ===============================================================================