Patrick, > done.. now getting > > checking system logging daemon PID file... /var/run/rsyslogd.pid > checking networking references... > checking for system logging daemon... semget: No such file or directory > semop: Invalid argument > semget: No such file or directory > semop: Invalid argument > configure: error: system logging daemon not running Odd. This error should have occurred during the first attempt as well. The error means that neither a "syslogd" nor "rsyslogd" process is running. One of these processes has to be running in order for the LDM system to log messages to its log file. You can check for these logging daemon processes via the command "ps -ef | grep syslog". > guessing i'm missing a package, trying to find which one... > makes me miss the old ldm days lol :) Me too! :-) Regards, Steve Emmerson Ticket Details =================== Ticket ID: SUQ-395547 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.