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.
Benjamin Cotton wrote: > > Anne, > > I checked syslog.conf and it has exactly what's given on the LDM > installation site. It's the same machine that Eric ran. As far as the > pnga2area seg fault, right after the workshop we had run into the > problem of somehow the massive drive space on anvil was full. My remedy > for this was to remove the lines in pqact.conf that caused the decoders > to write to this file. What I've done now is I have put the -l verbage > back in and made a cronjob that removes the png.log file once a month. > Nothing has been installed or broken lately, to the best of my > knowledge. However, the Computing Systems Administrator has been doing > upgrades to the department computers all summer, and something might > have been offended then. > > I'm pretty sure the University itself hasn't done anything to halt file > sharing, since that is the vice of choice among the vast majority of > guys in my hall. As for the EAS department, I couldn't say. I don't > think anyone uses department computers for that to begin with, but you > can never tell with dirt science (read: geoscience) people. I'll ask > our sysadmin, but it may be a while until he can get back to me on it. > > In the meantime, I've got a hunch the problem (or at least part of it) > lies somewhere in the pqact.conf vicinity. The data I receive, by > looking doing ldmadmin watch, is only about 45 minutes latent. However, > in my files the data is often 10-12 or more hours late. > > Thanks, > Ben > Hi Ben, First, I noticed that syslogd wasn't running on your machine. So I went to start it, but found that FreeBSD uses some unique (nonstandard) setup. We do not yet support FreeBSD (but we're working on it), so I'm not yet sure how syslogd should be set up. But, my co-worker has some experience with FreeBSD. From him I found out that the best interim solution is to use the -l <logfile> option to the LDM programs. This is what I would suggest for you for now so that logging works properly. Tomorrow, I will continue on this further. I'll identify places to add the -l option, and take a look at the pqact.conf entries. And, I see that your latencies are bad. I'll take a look at that too. Did I hear your oyster joke and just forget it? Oldtimers disease is such a blessing - everything's always fresh and new! Anne -- *************************************************** Anne Wilson UCAR Unidata Program address@hidden P.O. Box 3000 Boulder, CO 80307 ---------------------------------------------------- Unidata WWW server http://www.unidata.ucar.edu/ ****************************************************