HowTo: Set an Environment Variable in Mac OS X - Terminal Only

-
(from : http://www.dowdandassociates.com/blog/content/howto-set-an-environment-variable-in-mac-os-x-terminal-only/)

The process of setting environment variables in the Terminal will be familiar to those with experience with Linux or UNIX. It involves editing files in /etc for global environment variables, and in your home directory for user specific environment variables.

Login shell vs non-login shell

A login shell is the shell that is started when you open a new terminal window. A non-login shell is when you start a sub-shell in the window, for example, typing bash when you have the bash shell running already.

Global PATH only

If you just want to edit the global PATH variable, you can put a file in /etc/paths.d with a the path you want to add. For example, we will create a file /etc/paths.d/ec2-api-tools and put the following in:

/etc/paths.d/ec2-api-tools

1
/opt/aws/ec2-api-tools/bin
Open a new Terminal and $PATH will reflect the change.

Bash

Setting environment variables

The format for setting an environment variable in the bash shell is KEY=value with no spaces around the equal sign. In addition, when putting it in a configuration file it is necessary to prepend it with export. The following is an example of how to set an environment variable in one of the configuration files, it also works on the command line; we will set the variable JAVA_HOME to /Library/Java/Home:

Terminal - hostname:~ user$

1
export JAVA_HOME=/Library/Java/Home

Login shell

First /etc/profile, then whichever of the following exists, trying them in order: ~/.bash_profile, ~/.bash_login, or ~/.profile

Non-login shell

/etc/bashrc, then ~/.bashrc

Have login shell read /etc/paths and /etc/paths.d

/etc/profile (Excerpt)

1
2
3
if [ -x /usr/libexec/path_helper ]; then
 eval `/usr/libexec/path_helper -s`
fi

Have login shell read /etc/bashrc and ~/.bashrc

/etc/profile (Excerpt)

1
2
3
if [ "${BASH-no}" != "no" ]; then
 [ -r /etc/bashrc ] && . /etc/bashrc
fi

~/.bash_profile (Excerpt)

1
[[ -f ~/.bashrc ]] && . ~/.bashrc

Setup /etc/profile.d

/etc/profile (Excerpt)

1
2
3
4
for sh in /etc/profile.d/*.sh ; do
        [ -r "$sh" ] && . "$sh"
done
unset sh

Terminal - hostname:~ user$

1
sudo mkdir /etc/profile.d

Resources

The following is the collection of all the changes above along with links to download them:

/etc/profile

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
# System-wide .profile for sh(1)

if [ -x /usr/libexec/path_helper ]; then
 eval `/usr/libexec/path_helper -s`
fi

if [ "${BASH-no}" != "no" ]; then
 [ -r /etc/bashrc ] && . /etc/bashrc
fi

for sh in /etc/profile.d/*.sh ; do
        [ -r "$sh" ] && . "$sh"
done
unset sh

/etc/bashrc

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
# System-wide .bashrc file for interactive bash(1) shells.
if [ -z "$PS1" ]; then
   return
fi

PS1='\h:\W \u\$ '
# Make bash check its window size after a process completes
shopt -s checkwinsize
# Tell the terminal about the working directory at each prompt.
if [ "$TERM_PROGRAM" == "Apple_Terminal" ] && [ -z "$INSIDE_EMACS" ]; then
    update_terminal_cwd() {
        # Identify the directory using a "file:" scheme URL,
        # including the host name to disambiguate local vs.
        # remote connections. Percent-escape spaces.
 local SEARCH=' '
 local REPLACE='%20'
 local PWD_URL="file://$HOSTNAME${PWD//$SEARCH/$REPLACE}"
 printf '\e]7;%s\a' "$PWD_URL"
    }
    PROMPT_COMMAND="update_terminal_cwd; $PROMPT_COMMAND"
fi

~/.bash_profile

1
2
3
4
5
# ~/.bash_profile

# This file is sourced by bash for login shells.  The following line
# runs your .bashrc and is recommended by the bash info pages.
[[ -f ~/.bashrc ]] && . ~/.bashrc

~/.bashrc

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
# ~/.bashrc
#
# This file is sourced by all *interactive* bash shells on startup,
# including some apparently interactive shells such as scp and rcp
# that can't tolerate any output.  So make sure this doesn't display
# anything or bad things will happen !


# Test for an interactive shell.  There is no need to set anything
# past this point for scp and rcp, and it's important to refrain from
# outputting anything in those cases.
if [[ $- != *i* ]] ; then
        # Shell is non-interactive.  Be done now!
        return
fi


# Put your fun stuff here.

Tcsh

Setting environment variables

For the tcsh shell, the format for setting an environment variable is setenv KEY value. The following is an example which will set the JAVA_HOME variable to /Library/Java/Home.

Terminal - [hostname:~] %

1
setenv JAVA_HOME /Library/Java/Home

Login shell

First /etc/csh.cshrc, then /etc/csh.login, then whichever of the following exists, trying in order: ~/.tcshrc, ~/.cshrc; then finally ~/.login.

Non-login shell

First /etc/csh.cshrc, then whichever of the following exists, trying in order: ~/.tcshrc, ~/.cshrc.

References

Parts of this series

이 블로그의 인기 게시물

둘 중 누군가 그녀를 죽였다, 범인 해설

-
사건을 현실적인 눈으로만 따진다면 왜 추리소설을 읽겠는가마는, 히가시노 게이고의 흥행성을 인정하는 나로서도 이 책에서 따로 봉인 설명까지 곁들인 것치고는 추리논리가 군색함을 피할 수 없다고 생각한다. 작가는 크게 두 가지 근거를 들어, 준이치가 범인이라는 결론을 만들어두고 독자들의 호기심을 끌었다. 그 두 가지 근거는 첫째, 약봉지 두 개가 모두 일정한 방향으로 오른손잡이가 뜯었다는 점 그리고 둘째, 반창고가 높은 곳에 있어 이를 꺼낼 만한 사람은 소노코 혹은 준이치의 키가 되어야 한다는 점을 들고 있다. (가요코는 키가 이들보다 작다고 기술되어있다.) 봉인 설명서에서도 이런저런 대화식으로 처리했지만 어쨌든 이 두 가지를 결정적 근거로 삼고 있다. 그런데 이 두 가지 사실을 범인 판단 기준으로 삼는다고 쳐도 소노코 자살설 또한 그대로 유력하게 된다. 왜냐하면 소노코가 사실상 양손잡이이기 때문이다. 소노코가 글을 쓰는 것과 같은 행동들은 오른손을, 또 몇몇 행동들은 왼손을 사용한다는 식으로 기술해서 아마 준이치가 소노코가 명확히 어떤 손잡이인지 몰랐거나 뚜렷하게 인식하지 못 했다는 것을 분명히 하기 위한 장치 (만일 준이치가 소노코가 어느 손잡이인지 알았다면 약봉지를 뜯을 때 주의할 수도 있었어! 라는 가능성을 차단하기 위한 장치)로 썼던 것 같은데, 어찌 되었든 결국 그런 식의 기술은 소노코를 양손잡이로 만들어버리고 말았다. 뭐, 특정 행동은 반드시 특정 손을 쓴다고 하는 식으로 우겨 볼 수 있겠지만, 어쨌든 소노코의 오빠나 가가 형사 또한 소노코가 약봉지를 뜯을 때 어느 손으로 뜯을지 확신하긴 어려운 상황이 설정된 셈이다. 다시 말해, 소노코는 사실상 양손잡이인데다가 만일 당시의 포즈나 행동에 의해 다른 손을 사용할 가능성도 있기 때문에 판단 근거중 하나가 대단히 모호한 상태로 남게 되어버린다. 또 한 가지 근거인 반창고를 꺼낼 수 있는 키높이에 대한 것은 소설에서도 어찌 보면 미미한 근거로 드러나고 있다. 발판 같은 것을 구해서 반창고...
자세한 내용 보기

How to set password authentication with ec2-user of AWS

-
In fact, it would be problem to change instances of AWS to invalidate pem file(s) when one or some of system administrators or server side programmers / engineers leaves your group or company. But managing all of pem files by only one authorized person, it would be risky and tedious to do the job when the number of servers grows. For this situation, the traditional password authentication is the way to be acceptable.     There are some articles and sites about adding a new user with password to LINUX (or UNIX) server operated on AWS, or just dealing with pem file of ec2-user. But it is not easy to find the related things about applying password authentication with ec2-user clearly, although it is easy to do. And the most articles end with just creating the password for ec2-user, but it may not work for asking password whenever doing login. So, I'm writing how to apply the password authentication to ec2-user (default user) of AWS (LINUX / UNIX). Please do the f...
자세한 내용 보기

Start an Apache Web Server in Mac OS X Mavericks & Mountain Lion

-
이미지
Start an Apache Web Server in Mac OS X Mavericks & Mountain Lion The Sharing preference panel options were changed a bit in OS X Mountain Lion and again in Mavericks, and while things like Internet Sharing remain, the Web Sharing preference panel was removed. The Apache web server remains bundled with Mac OS X though, but you’ll need to turn to the command line to enable the web server. Additionally, you’ll want edit a user configuration file for each user account on the Mac to have the personal web sharing feature active. If any of this sounds intimidating or complex, it’s really not, just follow along and you’ll have a simple web server running on your Mac in no time. Setting Up and Starting the Apache Web Server in OS X Versions of OS X prior to Mountain Lion and Mavericks can simply turn on “Web Sharing”, but from 10.8 and 10.9 onward you’ll need to do the following to use a local web server: Launch Terminal, located in /Applic...
자세한 내용 보기