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.
Hi Ron, re: > I was wrong, the error message is a little different. Now the first error > line says this: > > hupsyslog: kill -HUP 936: Permission denied > > The following lines are the same. Assuming that nothing has changed on your machine since you sent us the ldm.zip file yesterday, the problem would appear to be that the PID for the system logging daemon (rsyslogd) contained in /var/run/syslogd.pid is different from the PID for the running system logging daemon: hupsyslog: kill -HUP 936: Permission denied <- 936 should be the content of syslogd.pid root 947 1 0 16:38 ? 00:00:00 /usr/sbin/rsyslogd -n I think that the easiest/fastest thing to do at this point is to reboot your machine. Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: HZS-503248 Department: Support LDM Priority: Normal Status: Closed =================== 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.