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

[LDM #LTH-656578]: decoders

Hi Marty,

> Rebuild is done. I sudo from another account on titan to "make root-actions"

Since you can become 'root' via sudo, please do the following:

-- become 'root'

cd /etc

-- edit rsyslog.conf and


# Unidata LDM:
local0.debug    /root/var/logs/ldmd.log


# Unidata LDM:
local0.debug    /data/logs/ldmd.log

After this editing change is complete, the user 'ldm' needs to
run 'hupsyslog':

<as 'ldm'>

-- after /etc/rsyslog.conf has been modified


'hupsyslog' sends a HUP signal to the syslog daemon telling it
to close all open files; reread its configuration file (/etc/rsyslog.conf);
and open all files again.  The change above tells 'rsyslog' to log to
the LDM log file which is (because I created it) located in /data/logs.

After these changes have been made, the LDM can be started again:

<as 'ldm'>

ldmadmin start


I made the following changes:

<as 'ldm'>

cd ~ldm
rm -rf data logs

ln -s /data data
mkdir /data/logs
ln -s /data/logs logs

The set of soft links now in place are:

~ldm/var/logs   -> ~ldm/logs -> /data/logs
~ldm/var/queues -> ~ldm/data -> /data
~ldm/var/data   -> ~ldm/data -> /data

I expect that when the LDM is restarted that you will start seeing
directories being created under /data.


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

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.