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

20050301: LDM - rpc.ldm & hupsyslog

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: 20050301: LDM - rpc.ldm & hupsyslog
  • Date: Tue, 01 Mar 2005 16:52:34 -0700
>From: "Jeremy Keen" <address@hidden>
>Organization: Ensco, Inc.
>Keywords: 200503011603.j21G39S8021981 LDM Linux LS_COLORS

Jeremy,

>Institution: Ensco Inc
>Package Version: 6.2.1
>Operating System: Mandrakelinux 10.1
>Hardware Information: hp pavilion ze5000
>Inquiry: Why is it that my hupsyslog and rpc.ldmd files in the bin
>directory show up highlighted red when it seems that my ldm is running fine?

Linux uses an enviornment variable, LS_COLORS, to colorize 'ls' listings.
It does this by aliasing the 'ls' command; here is an example:

alias ls='ls --color=tty'

(type 'alias' while logged in as the user running your LDM)

The default colorization scheme used tries to highlight exectables that
are setuid 'root' in red; the colorization has nothing to do with how
an executable is running.  This colorization can be changed by folks
that are interested in their own colorization scheme, or it can be
turned off using:

unalias ls

Check relevant man pages on your system for more information.

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.