[SOLVED] In which file are aliases stored?

postcd · 04-11-2016, 07:17 AM

Hello,

please kindly help me to find the file where are alias stored.

I DO NOT wish to update the alias file using command:
alias something="command"
because when i do it and exit that VPS back to node server, it no longer works next day.

but i want to know which file need to be updated.

I will be adding this line:
alias whoowns '/scripts/whoowns '

Currently whoowns command do not works and i already added that line into files:

.bashrc
.cshrc
.tcshrc

At the end of "man alias" i see: "GNU Bash-4.0"

The OS is: CentOS release 6.7 (Final)

tronayne · 04-11-2016, 07:36 AM

Aliases typically go into a file in your home directory that is executed once when you log in to your account.

They look like this:

Code:

alias lc='/usr/bin/clear; /bin/ls ${LS_OPTIONS} -aCF'
alias ll='/bin/ls ${LS_OPTIONS} -al'
alias cls='clear'
alias hi='history -${LINES}'
alias rs='eval `resize`'

(those are mine, yours will vary).

They can go into ./.profile if you want to cover all the bases (it is the first thing executed when you log in). You mention .cshrc in your post -- note that shell-compatible aliases (sh, BASH, KornShell) will not be compatible with C-Shell syntax (and vice-versa).

Hope this helps some.

TB0ne · 04-11-2016, 08:04 AM

Quote:

Originally Posted by postcd

Hello,
please kindly help me to find the file where are alias stored.

I DO NOT wish to update the alias file using command:
alias something="command"
because when i do it and exit that VPS back to node server, it no longer works next day.

but i want to know which file need to be updated.

I will be adding this line:
alias whoowns '/scripts/whoowns '

Currently whoowns command do not works and i already added that line into files:

.bashrc
.cshrc
.tcshrc

At the end of "man alias" i see: "GNU Bash-4.0" The OS is: CentOS release 6.7 (Final)

Here's something that should help:
http://lmgtfy.com/?q=how+to+add+alia...entos+6.7+bash

The very first link...of over 111,000.

Habitual · 04-11-2016, 08:53 AM

Put your aliases on the VPS in /home/user/.myaliases
Put in /home/user/.bashrc

Code:

source /home/user/.myaliases

type

Code:

source /home/user/.bashrc

and your aliases from /home/user/.myaliases will show up and be present on re-connect to the VPS.

Do I have to explain that the "user" in /home/user is the ssh user?

3 Years... sad.

TB0ne · 04-11-2016, 09:19 AM

Quote:

Originally Posted by Habitual

Put your aliases on the VPS in /home/user/.myaliases
Put in /home/user/.bashrc

Code:

source /home/user/.myaliases

type

Code:

source /home/user/.bashrc

and your aliases from /home/user/.myaliases will show up and be present on re-connect to the VPS.

Do I have to explain that the "user" in /home/user is the ssh user?
3 Years... sad.

Agreed.

However, your use of sourcing the .myaliases file isn't something I'd have thought of doing, and it makes sense. I'd just shovel things directly into my .bashrc file.

Habitual · 04-11-2016, 09:44 AM

Quote:

Originally Posted by TB0ne

Agreed.

However, your use of sourcing the .myaliases file isn't something I'd have thought of doing, and it makes sense. I'd just shovel things directly into my .bashrc file.

My use of ".myaliases" is merely for the seemingly under-experienced.
The correct answer to "In which file are aliases stored?" is any where you choose.

I use to have a need to reconcile moving targets, and in my case, my alias file actually contain the
"ssh -i key user@dom.com" parameters for a few clients. Plus I'm very type A, and after years of a single .bashrc,
it just got to be too monolithic. So now I stick everything work-related in ".all.c9aliases" instead of listing them
all in .bashrc

Code:

# source /home/jj/.ssh/c9/hosts/c9.hosts
# source /home/jj/.ssh/c9/hosts/client1.hosts
# source /home/jj/.ssh/c9/hosts/client2.hosts
# source /home/jj/.ssh/c9/hosts/client3.hosts
# source /home/jj/.ssh/c9/hosts/client4.hosts
# source /home/jj/.ssh/c9/hosts/client5.hosts
# source /home/jj/.ssh/WSM/wsm.hosts
# source /home/jj/.ssh/c9/hosts/client6.hosts
# source /home/jj/.ssh/c9/hosts/client7.hosts

vs.

Code:

source /home/jj/.ssh/c9/all.c9aliases

I hope this serves to illustrate how flexible the options are.

Resources:

Code:

man bash

References:
http://www.tldp.org/HOWTO/Bash-Prompt-HOWTO/x237.html
http://tldp.org/LDP/abs/html/aliases.html

Emerson · 04-11-2016, 09:46 AM

In addition alias whoowns '/scripts/whoowns ' will not work, unless you really have /scripts directory - you shouldn't.

onebuck · 04-16-2016, 12:37 PM

Hi,

From 'man bash';

Quote:

When an interactive shell that is not a login shell is started, bash reads and executes commands from ~/.bashrc, if that file exists. This
may be inhibited by using the --norc option. The --rcfile file option will force bash to read and execute commands from file instead of
~/.bashrc.

My preferences are to use '~/.bashrc' but you could use the '--rcfile file' option to insure the file you wish to use for the alias to be stored.

Hope this helps.
Have fun & enjoy!