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

[LDM #GRU-156569]: rsyslog rather than syslog

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: [LDM #GRU-156569]: rsyslog rather than syslog
  • Date: Sun, 02 Dec 2007 22:16:05 -0700
Hi Michael,

re:
> Description of problem: I don't know whether you are aware of this or not, but
> the latest fedora package, i.e., fc8 no longer  includes syslog or 
> syslog.conf.
> Instead, rsyslog and rsyslog.conf replaces it.  Manual pages for rsyslog note 
> the
> improvements in the newer utility but also warn users that rsyslog may not 
> behave
> as syslog.

I ran into this right after my workstation was upgraded from Fedora Core 5 to
Fedora 8 on Monday, November 26.  I found that the change needed to support 
Fedora
8 was small -- add a new section to the ~ldm/ldm-x.x.x/src/configure file.  The
needed change will be folded into a new LDM release.  We do not yet have an ETA
for the next LDM release.

Here is the change you need to make to ~ldm/ldm-6.6.5/src/configure:

 ...

    elif test -f /var/run/syslogd.pid; then
        cat >>confdefs.h <<\_ACEOF
#define SYSLOG_PIDFILE "/var/run/syslogd.pid"
_ACEOF

    # 20071126 - new section for rsyslogd
    elif test -f /var/run/rsyslogd.pid; then
        cat >>confdefs.h <<\_ACEOF
#define SYSLOG_PIDFILE "/var/run/rsyslogd.pid"
_ACEOF

 ...


> Apparently this affects the operation of the configuration file, producing an
> error requiring changes to the configuration file itself for correct 
> compiling.

The error I saw was when the LDM is started:

[ldm@yakov ~]$ ldmadmin start
The product-queue is OK.
/local/ldm/etc/pqact.conf is syntactically correct
sh: /etc/killall: No such file or directory
hupsyslog: system("/etc/killall -HUP syslogd") returns 32512
(E.G. It didn't work. Check that this program is setuid)
Starting the LDM server...

Is this the same thing that you saw?  If yes, the change to configure that I 
included
above will fix the problem.  Please remember that you will need to rebuild the 
LDM
from scratch after making the change to 'configure':

<as ldm>
cd ~ldm/ldm-6.6.5/src
make distclean
-- edit configure and add the small change I indicated above
./configure
make
make all
sudo make install_setuids

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: GRU-156569
Department: Support LDM
Priority: Normal
Status: Closed