Welcome to the most active Linux Forum on the web.
Go Back > Forums > Non-*NIX Forums > Programming
User Name
Programming This forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.


  Search this Thread
Old 04-30-2011, 06:51 PM   #1
LQ Newbie
Registered: Nov 2006
Posts: 29

Rep: Reputation: 0
How to run my C program from anywhere within the System (Ubuntu 10.10)?

I want to add my C program's path to the environment variable PATH. My C program called "md5". So that I can execute it from anywhere (i.e any directory).

My md5 program is located at "/home/ahuq/MappingServer/md5_program". So what I did was to put: "export PATH=$PATH:/home/ahuq/MappingServer/md5_program" in the running SHELL. This only makes temporary changes and lets me run the "md5" program from anywhere temporarily.

root@ahuq-kitchen:/home/ahuq# md5 -sanis
MD5 ("anis") = 38a1ffb5ccad9612d3d28d99488ca94b

But I want to make this change permanent.

I tried to put the line "PATH=$PATH:/home/ahuq/MappingServer/md5_program" at the end of "/home/ahuq/.bashrc" and "/home/ahuq/.profile" files. I logged out of the SHELL and
went in again. But it didn't work:

root@ahuq-kitchen:/home/ahuq# md5 -sanis
No command 'md5' found, did you mean:
Command 'cd5' from package 'cd5' (universe)
Command 'mdu' from package 'mtools' (main)
Command 'mdb' from package 'mono-debugger' (universe)
md5: command not found

Maybe I am putting the PATH statement in the wrong place of the above mentioned files. There are a lot if-else-fi structures inside those two files. Do I need to put the PATH statement inside any of those structures? Do I just logout or do I have to restart the system to make the changes active?

Old 04-30-2011, 07:07 PM   #2
Registered: Mar 2004
Location: VCO
Distribution: Arch
Posts: 43

Rep: Reputation: 26
Put that modified PATH line in /etc/environment
More on the subject
Old 04-30-2011, 07:13 PM   #3
LQ Newbie
Registered: Nov 2006
Posts: 29

Original Poster
Rep: Reputation: 0
I tried putting in: "export PATH=$PATH:/home/ahuq/MappingServer/md5_program" at the end of "/home/ahuq/.bashrc" and "/home/ahuq/.profile" files do not help. The contents of .bashrc file:
# ~/.bashrc: executed by bash(1) for non-login shells.

# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)

# for examples

# If not running interactively, don't do anything

[ -z "$PS1" ] && return

# don't put duplicate lines in the history. See bash(1) for more options

# ... or force ignoredups and ignorespace


# append to the history file, don't overwrite it

shopt -s histappend

# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)



# check the window size after each command and, if necessary,

# update the values of LINES and COLUMNS.

shopt -s checkwinsize

# make less more friendly for non-text input files, see lesspipe(1)

[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"

# set variable identifying the chroot you work in (used in the prompt below)

if [ -z "$debian_chroot" ] && [ -r /etc/debian_chroot ]; then

    debian_chroot=$(cat /etc/debian_chroot)


# set a fancy prompt (non-color, unless we know we "want" color)

case "$TERM" in

    xterm-color) color_prompt=yes;;


# uncomment for a colored prompt, if the terminal has the capability; turned

# off by default to not distract the user: the focus in a terminal window

# should be on the output of commands, not on the prompt


if [ -n "$force_color_prompt" ]; then

    if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then

	# We have color support; assume it's compliant with Ecma-48

	# (ISO/IEC-6429). (Lack of such support is extremely rare, and such

	# a case would tend to support setf rather than setaf.)






if [ "$color_prompt" = yes ]; then

    PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '


    PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '


unset color_prompt force_color_prompt

# If this is an xterm set the title to user@host:dir

case "$TERM" in


    PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1"





# enable color support of ls and also add handy aliases

if [ -x /usr/bin/dircolors ]; then

    test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"

    alias ls='ls --color=auto'

    #alias dir='dir --color=auto'

    #alias vdir='vdir --color=auto'

    alias grep='grep --color=auto'

    alias fgrep='fgrep --color=auto'

    alias egrep='egrep --color=auto'


# some more ls aliases

alias ll='ls -alF'

alias la='ls -A'

alias l='ls -CF'

# Alias definitions.

# You may want to put all your additions into a separate file like

# ~/.bash_aliases, instead of adding them here directly.

# See /usr/share/doc/bash-doc/examples in the bash-doc package.

if [ -f ~/.bash_aliases ]; then

    . ~/.bash_aliases


# enable programmable completion features (you don't need to enable

# this, if it's already enabled in /etc/bash.bashrc and /etc/profile

# sources /etc/bash.bashrc).

if [ -f /etc/bash_completion ] && ! shopt -oq posix; then

    . /etc/bash_completion


#my program's path
export PATH=$PATH:/home/ahuq/MappingServer/md5_program

---------- Post added 05-01-11 at 06:14 AM ----------

The contents of my .profile file is:

# ~/.profile: executed by the command interpreter for login shells.

# This file is not read by bash(1), if ~/.bash_profile or ~/.bash_login

# exists.

# see /usr/share/doc/bash/examples/startup-files for examples.

# the files are located in the bash-doc package.

# the default umask is set in /etc/profile; for setting the umask

# for ssh logins, install and configure the libpam-umask package.

#umask 022

# if running bash

if [ -n "$BASH_VERSION" ]; then

    # include .bashrc if it exists

    if [ -f "$HOME/.bashrc" ]; then

	. "$HOME/.bashrc"



# set PATH so it includes user's private bin if it exists

if [ -d "$HOME/bin" ] ; then



export PATH=$PATH:/home/ahuq/MappingServer/md5_program

Last edited by anis_huq; 05-02-2011 at 02:07 AM.
Old 04-30-2011, 07:19 PM   #4
LQ Newbie
Registered: Nov 2006
Posts: 29

Original Poster
Rep: Reputation: 0
found it. put the "export PATH=$PATH:/home/ahuq/MappingServer/md5_program" line in:
/etc/bash.bashrc and problem solved!
Old 04-30-2011, 07:27 PM   #5
LQ Newbie
Registered: Nov 2006
Posts: 29

Original Poster
Rep: Reputation: 0
Thanks @ DarkVenger .........
Old 04-30-2011, 07:42 PM   #6
LQ Guru
Registered: Mar 2004
Distribution: SusE 8.2
Posts: 5,863
Blog Entries: 1

Rep: Reputation: Disabled
Hi -

Glad you got it working. And changing /etc/bash.bashrc is definitely the way to go to modify the $PATH for all users.

However, "/home/ahuq/.bashrc" and "/home/ahuq/.profile" should have worked, too. It didn't look like you had any syntax errors, and there shouldn't be any "special place" you needed to put your changes. You shouldn't have to restart the system ... but you *should* log out from and log back in to your entire GUI session. Or, equivalently, log in from another "virtual terminal" (e.g. <Ctl-Alt-F1>. Either way, it should have read your modified local environment and given you the new $PATH.
Old 04-30-2011, 07:52 PM   #7
LQ Guru
Registered: Aug 2001
Location: Fargo, ND
Distribution: SuSE AMD64
Posts: 15,733

Rep: Reputation: 677Reputation: 677Reputation: 677Reputation: 677Reputation: 677Reputation: 677
You could have put it in your ~/.profile file, and exported it. Not exporting PATH is why it didn't work originally. Using .profile or .bash_login (which ever one you use) is better than .bashrc because .bashrc will be run again whenever you create a subshell, adding the same directory to your PATH variable for each subshell. The .profile script will be sourced once when you log in.

For programs and scripts you do yourself, you can also put them in $HOME/bin/ which should be in $PATH already instead of changing a system directory or file.
1 members found this post helpful.
Old 05-01-2011, 09:55 AM   #8
LQ 5k Club
Registered: Sep 2009
Posts: 6,443
Blog Entries: 3

Rep: Reputation: 721Reputation: 721Reputation: 721Reputation: 721Reputation: 721Reputation: 721Reputation: 721
@ anis_huq

Edit post #3 to use [code]code goes here[/code] tags. And use code tags from now on whenever posting code or command output.
Old 05-02-2011, 02:17 AM   #9
LQ Guru
Registered: Mar 2004
Distribution: SusE 8.2
Posts: 5,863
Blog Entries: 1

Rep: Reputation: Disabled
@mtk358 -

Didn't your mommy ever teach you the importance of using words like "Please" and "Thank you"?


environment variable, shell, ubuntu+10.10

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
How to run system file checker on ubuntu 10.10 without damaging the system mansour Linux - Newbie 18 04-10-2011 11:53 AM
how to run vb program on ubuntu ? shridhar005 Linux - Software 3 04-24-2009 03:39 PM
to run program on remote system ashu283 Linux - Networking 2 10-19-2005 03:30 AM
how can i access windows system just sa i do // in the run program in wind sibu_rajappan Linux - General 4 05-28-2004 07:56 AM
program to run whne system shuts down jayakrishnan Linux - General 1 10-15-2003 06:39 AM > Forums > Non-*NIX Forums > Programming

All times are GMT -5. The time now is 09:49 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration