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

[LDM #SWB-825395]: LDM question: sticky bit

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: [LDM #SWB-825395]: LDM question: sticky bit
  • Date: Wed, 27 Sep 2017 15:27:20 -0600
James,

> We're using a very old version of the LDM and are starting to "refresh"
> our LDM environment. We've found our LDM log files are owned by root and
> traced this to the fact that ldmd has the sticky bit set.

Something's wrong. The ldmadmin(1) script should create the LDM log file with 
the LDM user as the owner regardless of the ownership of the LDM server, 
ldmd(1). At least, that's what happens now. How old is your version?

> What is the
> reason for this? Would removing it cause the LDM to lose functionality?

The LDM program must be owned by root and setuid in order for it to listen on 
its well known (and registered) port, 388. As soon as it obtains this port from 
the operating system, it relinquishes root privileges.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: SWB-825395
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.