Donna, OK. We understand your problem. There are, basically, two solutions: 1. Replace the use of syslog-ng(8) with syslogd(8); or 2. Rewrite the LDM package's configuration-script and LDM administration script to use syslog-ng(8) rather than syslogd(8). The second solution will require work on your part and render your LDM installation non-standard and, therefore, harder to support. The first solution, on the other hand, should be easily accomplished via a SUSE RPM for syslogd(8), which can be obtained from http://search.novell.com/qfsearch/HighlightServlet?&query=syslogd+rpm&index=Novell&bbindex=BestBets&lang=&encoding=iso-8859-1&url=http%3A%2F%2Fwww.novell.com%2Fproducts%2Flinuxpackages%2Fenterpriseserver%2FSP2%2Fi386%2Fsyslogd.html (or you might just go to "suse.com" and enter "syslogd rpm" in the search box in the upper right corner.) It might also be possible to use the yum(1) utility to install the syslogd(8) package (we don't know because we don't use SUSE). If you choose to go this route, then once you have the syslog daemon installed and running, then you can configure and use it as documented in the LDM web pages. Regards, Steve Emmerson
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.