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

Re: 20050824:ldm startup

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: 20050824:ldm startup
  • Date: Wed, 24 Aug 2005 12:21:20 -0600
Eric,

> To: Unidata Support <address@hidden>
> From: Eric Nelson <address@hidden>
> Subject: ldm startup.
> Organization: UCAR/RAP
> Keywords: 200508241720.j7OHK4jo005879

The above message contained the following:

> If I see the following when starting my ldm...
> 
> hupsyslog: kill -HUP 3871: Permission denied
> 
> does this mean that make install_setuids encountered a problem or was not 
> executed as root?

Probably.  You can check via the command

    ls -l $LDMHOME/bin/hupsyslog

It should show that the file is owned by "root" and set-uid, e.g.,


    -rwsr-xr-x   1 root     ustaff     42640 Jun 30 08:11 
/home/steve/ldm/package/bin/hupsyslog

> Supposedly the sysadmin executed make install_setuids 
> since they don't like giving scientists root access.

If that step was skipped, then the files "hupsyslog" and "rpc.ldmd" will
still exist in the "bin/" subdirectory, but they won't be owned by root
or set-uid.

> Eric Nelson
> 
> National Center for Atmospheric Research
> Research Applications Laboratory
> http://www.ral.ucar.edu
> address@hidden
> (303) 497-2838
> 
> "I love deadlines.  I especially like the whooshing sound they make as
> they go flying by."     --Douglas Adams

Regards,
Steve Emmerson

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