because I can see in one app that we have locally, that a user login with a specific user that, this user needs to type
, to access the application
Perhaps in this "bashrc" there are some settings the user needs to start the application.
Note, though, that ".bashrc" and "bashrc" is not the same! The first one is the one which gets executed (automatically) every time the bash shell starts. The second one is just an ordinary file with a similar-looking name.
Further, in standard UNIX the current directory is not part of the PATH, so when you enter "bashrc" without anything, chances are you do not execute the file named "bashrc" in the current directory but an identically named file located elsewhere. Enter
Hi Gurus!
I recently got my shell account (HP UX v11) created by our sysadmin and am having problem deleting with the backspace key.
After doing some reading, I believe I need to enter a custom "STTY..." statement in my profile.
Can someone please help me with the correct "STTY" sequence... (3 Replies)
Hi
Can anyone tell me if it is at all possible to edit ones .bash_profile, to make the setting on of line numbers (in vi/vim), permanent?
I've been to a few IRC channels and people keep telling me it is more of a vi/vim thing and to use something called ".vimrc", however I heard that it is... (3 Replies)
Dear experts,
I have installed Ruby in the following directory:
$ pwd
/home/ewijaya/.ruby
$ ls
bin lib share
And I have also stated the PATH in my bash_profile like this:
# .bash_profile
# Get the aliases and functions
if ; then
. ~/.bashrc (1 Reply)
Hi Guys,
I modified my .bash_profile script , and tried to change the prompt.
Following is the line of code in my .bash_profile script.
export PS1=" \W "
But I get the output as:
\W
This appears to be my prompt now.
Any idea what should be done..
Thanks! (0 Replies)
We are more users using the oracle account, and people want to include theyr own files in .bash_profile. Like this:
while ; do
echo -n "LOGNAME is '$LOGNAME' (no sens), who are you? " >/dev/stderr
read ln
export LOGNAME=$ln
done
This works well when logging in to... (1 Reply)
Hi all. when i connect as user megaguru i have a problem my .bash_profile does not working^:(
if i do:
. ./.bash_profile
all enviroment variables are in place. How can i force linux to use .bash_profile before logon process?
thanx in advance. (1 Reply)
I am using solaris 10 x86. I have created a .bash_profile under root's home directory(/). The contents of the file are:
Solaris10u8/# cat .bash_profile
export PATH=$PATH:/usr/sfw/bin
export PS1='\h\w\$ '
export PAGER="less -imsq"
alias ll='ls -l'
alias la='ls -a'
The problem is that:
... (7 Replies)
Hi,
happy new year.
on AIX 6.1 , for user oracle , there are two files :
bash_profile and .profile
I do not know which one is executed when login ? How to know ,
More over in both of them we have :
in .profile :
ORACLE_HOME=/appli/oracle/product/10.2.0/db_1... (5 Replies)
Hi All
I am kind of confused, when to use .bash_profile or .profile
I have just created a user on a test server, with:
useradd -u 103 -d /fretagi -m -s /bin/bash fretagi
but now in its home dir I have:
-bash-3.2$ ls -al
total 14
drwxr-xr-x 2 fretagi other 512 Dec 5 15:54 .... (5 Replies)
Hello everyone,
I'm trying to set my .bash_profile to change my primary prompt from this:
banbatchtest1v:MCPPRD:~>to this:
banbatchtest1v:MCPPRD:/home/rcarvall>
Here's what my .bash_profile looks like right now:
# .bash_profile
# Get the aliases and functions
if ; then
.... (2 Replies)
Discussion started by: galileo1
2 Replies
LEARN ABOUT MINIX
locale
LOCALE(1) Linux User Manual LOCALE(1)NAME
locale - get locale-specific information
SYNOPSIS
locale [option]
locale [option] -a
locale [option] -m
locale [option] name...
DESCRIPTION
The locale command displays information about the current locale, or all locales, on standard output.
When invoked without arguments, locale displays the current locale settings for each locale category (see locale(5)), based on the settings
of the environment variables that control the locale (see locale(7)). Values for variables set in the environment are printed without dou-
ble quotes, implied values are printed with double quotes.
If either the -a or the -m option (or one of their long-format equivalents) is specified, the behavior is as follows:
-a, --all-locales
Display a list of all available locales. The -v option causes the LC_IDENTIFICATION metadata about each locale to be included in
the output.
-m, --charmaps
Display the available charmaps (character set description files). To display the current character set for the locale, use locale
-c charmap.
The locale command can also be provided with one or more arguments, which are the names of locale keywords (for example, date_fmt, ctype-
class-names, yesexpr, or decimal_point) or locale categories (for example, LC_CTYPE or LC_TIME). For each argument, the following is dis-
played:
* For a locale keyword, the value of that keyword to be displayed.
* For a locale category, the values of all keywords in that category are displayed.
When arguments are supplied, the following options are meaningful:
-c, --category-name
For a category name argument, write the name of the locale category on a separate line preceding the list of keyword values for that
category.
For a keyword name argument, write the name of the locale category for this keyword on a separate line preceding the keyword value.
This option improves readability when multiple name arguments are specified. It can be combined with the -k option.
-k, --keyword-name
For each keyword whose value is being displayed, include also the name of that keyword, so that the output has the format:
keyword="value"
The locale command also knows about the following options:
-v, --verbose
Display additional information for some command-line option and argument combinations.
-?, --help
Display a summary of command-line options and arguments and exit.
--usage
Display a short usage message and exit.
-V, --version
Display the program version and exit.
FILES
/usr/lib/locale/locale-archive
Usual default locale archive location.
/usr/share/i18n/locales
Usual default path for locale definition files.
CONFORMING TO
POSIX.1-2001, POSIX.1-2008.
EXAMPLE
$ locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
$ locale date_fmt
%a %b %e %H:%M:%S %Z %Y
$ locale -k date_fmt
date_fmt="%a %b %e %H:%M:%S %Z %Y"
$ locale -ck date_fmt
LC_TIME
date_fmt="%a %b %e %H:%M:%S %Z %Y"
$ locale LC_TELEPHONE
+%c (%a) %l
(%a) %l
11
1
UTF-8
$ locale -k LC_TELEPHONE
tel_int_fmt="+%c (%a) %l"
tel_dom_fmt="(%a) %l"
int_select="11"
int_prefix="1"
telephone-codeset="UTF-8"
The following example compiles a custom locale from the ./wrk directory with the localedef(1) utility under the $HOME/.locale directory,
then tests the result with the date(1) command, and then sets the environment variables LOCPATH and LANG in the shell profile file so that
the custom locale will be used in the subsequent user sessions:
$ mkdir -p $HOME/.locale
$ I18NPATH=./wrk/ localedef -f UTF-8 -i fi_SE $HOME/.locale/fi_SE.UTF-8
$ LOCPATH=$HOME/.locale LC_ALL=fi_SE.UTF-8 date
$ echo "export LOCPATH=$HOME/.locale" >> $HOME/.bashrc
$ echo "export LANG=fi_SE.UTF-8" >> $HOME/.bashrc
SEE ALSO localedef(1), charmap(5), locale(5), locale(7)COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the
latest version of this page, can be found at https://www.kernel.org/doc/man-pages/.
Linux 2017-09-15 LOCALE(1)