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

20050804: Installing LDM on Fedora Core 3 64-bit (cont.)



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

Nancy,

re: problems
>       Well the major change was to the ldmadmin-pl.conf file where it
>had asked for the OS and release.  I had used the wrong single quote for
>the $os=`uname -s` and release line.  So, it had not correctly
>picked up the information.  Obviously a huge mistake.

Those two lines:

#
# The operating system environment:
#
chop($os = `uname -s`);
chop($release = `uname -r`);

are not designed to be modified by the end user.  They are designed to
pickup needed information from the operating system and then used to
setup various items.  By the way, the entries in
~ldm/etc/ldmadmin-pl.conf are not used in the build process, so they
could have nothing to do with the hupsyslog problems you were seeing.

>       Every time we ran the configure, it refused to change
>permissions for hupsyslog and rpc.ldmd saying the operation was not
>permitted.

I am confused.  'configure' creates the makefile in ~ldm/ldm-6.3.0/src.
It does not change permissions on hupsyslog.

>We were in as LDM user, and when we typed the su -c ldm make
>install_setuids  command, it came back as unknown user.  We finally
>figured out we had to be root to do that, and the syntax was backward.
>We had to enter:
>su -c make install_setuids ldm

Correct.  The step to set needed file permissions on hypsyslog and
rpc.ldmd are:

<as 'root'>
cd ~ldm/etc/ldm-6.3.0/src
make install_setuids

The full process is:

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

<as 'root'>
cd ~ldm/etc/ldm-6.3.0/src
make install_setuids

<as 'ldm'>
cd ~ldm
ln -s ldm-6.3.0 runtime
ln -s runtime/* .

>       Here is the ldmd.conf file.  I can't see any errors.

Errors may be hard to spot.  The best way to find errors in
~ldm/etc/ldmd.conf is by reviewing the log output from an attempted
start.  This requires logging to be working; my previous
recommendations apply.

>I have used tabs in the request lines.

Tabs are not crutial in ~ldm/etc/ldmd.conf.  They are crutial in
~ldm/etc/pqact.conf.

>Basically I took the one I was using on
>mothra, and ftped it over to Godzilla.

I can't see any problem in your ldmd.conf file.

Given how long your problem has lingered, I would like to be able
to login to your machine to look at the setup.  Is this possible?

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.