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

20050411: ownership/permissions check...



>From: Darren Addy <address@hidden>
>Organization: University of Nebraska at Kearney
>Keywords: 200504111924.j3BJOWv2023220

Hi Darren,

>Greetings and thanks for your answer earlier today.
>Hoping I can get this off to you before 5 PM (your time).
>: )
>
>I've successfully installed LDM and it will start/run.
>I'm starting it AS the ldm user.
>I get one error:
>hupsyslog: couldn't open /var/run/syslogd.pid

This is most likely due to your not having changed the ownership
of the LDM routines 'hupsyslog' and 'rpc.ldmd' in the final
step of the LDM installation.  As a quick review, the process
for building the LDM are:

<as 'ldm'>
cd ~ldm

 -- setup your SHELL-specific configuration file (e.g., .cshrc for
    C shell, .bashrc for BASH, etc.) with the appropriate PATH
    information, define LDMHOME, etc.
 -- grab the current distribution

zcat ldm-6.3.0.tar.Z | tar xvf -
cd ldm-6.3.0/src
./configure
make
make install
sudo make install_setuids             <- if the user 'ldm' has sudo
                                         capability; if not 'root'
                                         will need to CD to the
                                         ~ldm/ldm-6.3.0/src directory
                                         and run 'make install_setuids'

cd ~ldm
rm -f runtime
ln -s ldm-6.3.0 runtime
ln -s runtime/bin bin
ln -s runtime/include include
ln -s runtime/lib lib
ln -s runtime/man man
ln -s runtime/src src

  -- setup ~ldm/etc/ldmd.conf 'request' lines for data
  -- setup ~ldm/etc/pqact.conf lines to process data
  -- ** setup scouring of data that you ingest **

>Searching your support archives, it sounded like this was due 
>to an ownership problem. I think I may have created it by doing
>(as root) a chmod -Rf ldm
>on the entire ldm directory. (Some items had been owned by root).
>Here is my current owner: group situation.
>Everything in runtime is owned by ldm:root
>Everything in ldm-6.3.0 is owned by ldm:root
>User "ldm" is part of a group called "wxserver".

When doing a global chmod, you should make sure that you include the
appropriate group.  For instance, since your 'ldm' is in the group
'wxserver', the chmod command you would execute should be:

<as 'root'>
cd ~ldm
chmod -R ldm:wxserver *

This will, however, change the ownership and permissions on 
~ldm/bin/hupsyslog and ~ldm/bin/rpc.ldmd.  This is what caused
your problem to begin with.

>If GEMPAK has a user, it will belong to the group "wxserver" also.
>Perhaps I should have changed a GROUP ownership?

Yup.

>Anyway, I stopped the LDM server and wanted to make sure that
>I had the ownership stuff set correctly before continuing.

Good move.  The easiest way to recover from the current state is to
have 'root' rerun the 'make install_setuids' step from the
~ldm/ldm-6.3.0/src directory.

>When that is done, I guess the next step is requesting the IDD feeds?

Yes.

>I'd like to begin with just HDS and NNEXRAD.

Please request those feeds from the UNL IDD node papagayo.unl.edu:

request HDS     ".*"    papagayo.unl.edu
request NNEXRAD ".*"    papagayo.unl.edu

Please remember that both the NNEXRAD and HDS feeds contain a good bit
of data.  If you don't need all of the data in the streams, you can
limit your request by changing the regular expression in the request
line to match the subset that you want/need.

>Darren Addy
>Multimedia Specialist, Office of I.T. Services
>University of Nebraska at Kearney
>214 Otto Olsen Bldg.

Cheers,

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