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.
Phil, In the src/ulog directory there is a README for the details. Do the following, you said that you are using local4 right? Test with the following csh script: % foreach level (err warning notice info) ? echo $level | logger -i -t test -p local4.$level ? end Your logfile should have some lines sortof like this: Jul 24 02:49:28 zeppo test[26767]: err Jul 24 02:49:28 zeppo test[26769]: warning Jul 24 02:49:28 zeppo test[26771]: notice Jul 24 02:49:28 zeppo test[26773]: info The log file must exist before syslog will write to it. A touch command on the ldmd.log file, also make sure the permission are correct. Also, after changes are made to /etc/syslog.conf a HUP signal is needed for syslog to reread the file. Also check that the syslogd is running. If logger writes to the ldmd.log file, try a LDM compile with environment var CC set as: % setenv CC 'cc -DLOG_LDM=LOG_LOCAL4' You need to do a recompile starting with a clean distribution so the old configurations are not used. Robb... On 7 Dec 1999, Phil Mieczynski wrote: > > Robb, > I forwarded your instructions on recompiling the source code to use the local0 > facility to one of our developers at the FO. We decided to use local4 since > local0 thru 3 were already being used. It didn't seem to work. I've included > the > latest email from the developer on this issue. Do you have any other > suggestions? ...Phil > > Sorry, I forgot to send you an email yesterday. I worked on it a little > and tried compiling it several times with modifications as suggested in > your original email but I had no luck, it seemed no matter how I tried, > it would never write to local4. Although syslogd recognized local4, > nothing I tried would get ldmd to write there. > > Out of ideas here... > Craig > > > ____________________Reply Separator____________________ > Subject: Re: 19991129: local0 facility > Author: address@hidden > Date: 11/30/99 2:40 PM > > On Mon, 29 Nov 1999, Unidata Support wrote: > > > >To: address@hidden > > >From: Phil Mieczynski <address@hidden> > > >Subject: local0 facility > > >Organization: . > > >Keywords: 199911292356.QAA21707 > > > > > > Hi Robb, > > > > I've been loading the HP-UX 10.20 binary distribution of LDM on several of > > our > > platforms. I just ran into a problem when trying to load the binary on a > > HP-UX > > 10.20 box that is running an application that is already using the local0 > > facility to log messages to a non-ldm file. > > > > The LDM Installation instructions say to add the following entry to > > /etc/syslog.conf > > local0.debug /usr/local/ldm/logs/ldmd.log > > > > The problem is that the /etc/syslog.conf file on the box in question already > has > > local0.debug /data/logs/dnlog > > > > I've spoken to the developer's of the dn app and they tell me that > local0.debug > > is hard coded into the application and would require a recompilation of the > > source to make a change. In other words, cows will fly before changes are > > made > > to this particular source code. > > > > My question is, can the local0 facility be changed on the binary > > distribution > of > > LDM that I currently have? If not, what options do I have? > > > > Phil, > > The local0 cannot be changed in the LDM binary release, it's hard coded as > well. There are 2 options, > > - use : > > local0.debug /usr/local/ldm/logs/ldmd.log in syslog.conf and expect the > log messages from the dn app to also be in the log file. This usually > isn't a problem if the dn app doesn't have many messages. > > - Build the LDM from source, in src/ulog.h > > change: > > ulog.h:#define LOG_LDM LOG_LOCAL0 > > to > > ulog.h:#define LOG_LDM LOG_LOCAL1 > > Then change the syslog.conf to local1 for the LDM > > Robb... > > > > Thanks...Phil > > > > =============================================================================== > Robb Kambic Unidata Program Center > Software Engineer III Univ. Corp for Atmospheric > Research > address@hidden WWW: http://www.unidata.ucar.edu/ > =============================================================================== > =============================================================================== Robb Kambic Unidata Program Center Software Engineer III Univ. Corp for Atmospheric Research address@hidden WWW: http://www.unidata.ucar.edu/ ===============================================================================