Re: [ldm-users] syslog woes in configuration script

• To: gt3rx3@xxxxxxxx, ldm-users@xxxxxxxxxxxxxxxx
• Subject: Re: [ldm-users] syslog woes in configuration script
• From: "Zickert, Glenn A" <glenn.a.zickert@xxxxxxxx>
• Date: Mon, 10 Mar 2008 13:16:59 -0600

Editing the configure script is OK for a temporary work-around but for
the formal release you should update the aclocal.m4 so that the
configure script can be rebuilt using "autoreconf -vi".  When I tried
this several other needed m4 scripts were missing.  These should also be
distributed so that the configure script can be properly built. 

-----Original Message-----
From: ldm-users-bounces@xxxxxxxxxxxxxxxx
[mailto:ldm-users-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Michael Allen
Sent: Wednesday, 27 February, 2008 05:28
To: ldm-users@xxxxxxxxxxxxxxxx
Subject: [ldm-users] syslog woes in configuration script

Solving ldm syslog/rsyslog issues requires simply replacing "syslog" 
with "rsyslog" references in the configure script then building ldm from
source.  Exchanging syslog with rsyslog system-wide will give you many
more issues, of course.

In my copy of the configure script the references look like this:

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

As I recall there are two places at about the 5800 ff line area.

Michael Allen
CPHS
_______________________________________________
ldm-users mailing list
ldm-users@xxxxxxxxxxxxxxxx
For list information or to unsubscribe,  visit:
http://www.unidata.ucar.edu/mailing_lists/ 

• References:
  • [ldm-users] syslog woes in configuration script
    • From: Michael Allen