Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   10987 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

nlspath(4)							    nlspath(4)

NAME
       nlspath - NLSPATH configuration file

DESCRIPTION
       The  file  allows  the  superuser  to  restrict the paths set by others
       through an environment variable to locate message catalogs for or  root
       programs.

       This file contains only one entry with the following format:

       pseudo-pathnames	 in this file should be absolute pathnames and must be
       separated by a colon.  The paths which are available both in  the  con‐
       figuration  file and environment variable are considered to locate mes‐
       sage catalog files.  The file should not be edited directly.   Instead,
       the  command  should  be used to modify the contents of this file.  See
       chnlspath(1M) for details.

       If contains the file is in compatibility mode.  In this case,  all  and
       root  programs  use the environment variable directly to locate message
       catalogs.  This configuration file is supported only to	provide	 back‐
       ward  compatibility  for	 those or root programs which are depending on
       the environment variable New or root programs should not depend on  the
       environment variable and configuration file

EXAMPLES
       An entry in this file would typically look like:

WARNINGS
       The configuration file must be root owned and there should not be write
       permission set for group and  others.   Superuser  should  not  provide
       write  permission  for  group and others for the paths mentioned in the
       configuration file.

       is provided only for compatibility with existing or  root  applications
       that make use of relative pathnames while invoking catopen(3C).	New or
       root  applications  must	 use   absolute	  pathnames   while   invoking
       catopen(3C).

       This file is to be obsoleted at a future date.

FILES
SEE ALSO
       catopen(3C), chnlspath(1M), environ(5).

				TO BE OBSOLETED			    nlspath(4)

Vote for polarhome