Gerry, By default, the new version doesn't use the system logging daemon -- but it can in order to be backward compatible; thus, the system logging daemon must still exist. Check the "/etc" directory for a configuration-file for the system logging daemon. > Gotta leave this one for today, but I'm still getting the logging > configuration-file not found error. For the record, this is using 188.8.131.52 > > vlogin02.ls5(40)$ ./configure --disable-root-actions > ... > checking for socklen_t... yes > checking for fsync... yes > checking for ftruncate... yes > checking for memmove... yes > checking for memcmp... yes > checking for rename... yes > checking for strerror... yes > checking for waitpid... yes > checking for strdup... yes > checking for seteuid... yes > checking for setenv... yes > checking for mmap... yes > checking for sigaction... yes > checking for sig_atomic_t in signal.h... defined > checking for an ANSI C-conforming const... yes > checking for struct stat.st_blksize... yes > checking system logging daemon PID file... /var/run/rsyslogd.pid > checking for system logging daemon... rsyslog > checking for /etc/rsyslog.conf... no > checking for /etc/opt/csw/rsyslog.conf... no > configure: error: system logging configuration-file not found or not > readable > vlogin02.ls5(40)$ pwd > /home1/00791/gcreager/LDM/ldm-184.108.40.206 > > -- > Gerry Creager Regards, Steve Emmerson Ticket Details =================== Ticket ID: JSH-709228 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.