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

20050726: New LDM installation (cont.)



>From: Nancy Selover <address@hidden>
>Organization: ASU
>Keywords: 200507190034.j6J0Ywjo000855 LDM install Fedora Core 3

Hi Nancy,

>Have you figured anything out yet from my logs I sent last Friday?  I
>have attached them again, in case you didn't get them before.

I hadn't noticed that you sent them on the 22nd, sorry.

>The "envir.txt" is the output from giving the "env" command in the LDM
>home directory.

OK.

I rechecked ~ldm/ldm-6.3.0/src/ulog/hupsyslog.c and reassured myself
that the only way that your executable can try to run killall is if the
SYSLOG_PIDFILE macro was not set.  This gets defined during the
'configure' step in the build, and it should be reflected in the file
config.log.  Given this, I went back and compared the end of your
config.log file and one from one of our FC3 systems; they are very
different:

your config.log:

 ...
#define SIZEOF_LONG 4
#define STDC_HEADERS 1
#define USE_GDBM 1
 ...

our systems config.log:

#define SIZEOF_LONG 4
#define STDC_HEADERS 1
#define SYSLOG_PIDFILE "/var/run/syslogd.pid"
#define ULOGNAME "/dev/log"
#define USE_GDBM 1

The culprit is that SYSLOG_PIDFILE is _not_ defined in yours (along
with ULOGNAME) while it is defined in ours.

I will need to forward this along to our LDM developer to see if
he understands why configure run on your system is significantly
different than on ours.  I will get back to you when I have had
a chance to talk with him.

In the meantime, try rebuilding:

<as 'ldm'>
cd ~ldm/ldm-6.3.0/src
make distclean
./configure
make

and let me know if this makes any difference.

Sorry for the delay...

Cheers,

Tom
--
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.


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.