[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: hupsyslog(1) using killall(1) under SUSE (was: LDM-6.4.1 instalation)

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.

  • Subject: Re: hupsyslog(1) using killall(1) under SUSE (was: LDM-6.4.1 instalation)
  • Date: Thu, 13 Oct 2005 16:32:48 -0600
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