07-21-2019
Both sets of commands define two variables that are available to everything running in the current shell execution environment.
The second set of commands (using export) also causes those two variables to be available to everything running in subshells and other execution environments initiated by the current shell execution environment after those variables are exported. Those variables will not be available to processes that were already running at the time those variables were exported no matter how those processes were initiated.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
:) as soon as i installed my software a couple of weeks ago..
(fedora core 2 vs, 2.6.8-1.521) i decided to switch the shell to sh shell and i know that .bashrc is the bash profile file(???) i want to use the sh version of the same file and make it the main profile file.. how can I switch it and... (3 Replies)
Discussion started by: moxxx68
3 Replies
2. UNIX for Dummies Questions & Answers
hey guys,
Im trying to find all my .bashrc files in the home directory.
~/etc/bash.bashrc is the only thing i can find but its outside of my /home
Could the files be hidden? I want to see all my .bashrc files in my /home structure... <cries> (5 Replies)
Discussion started by: oxoxo
5 Replies
3. UNIX for Dummies Questions & Answers
Hi,
I was instructed to find all the .bashrc files on my system, that MODIFY the PS1 varaible.
here is what i've come up with so far:
ls / .bashrc -print
woo.
But thats not all. I need to display the full file name ( Including the full path ) and protection.
- I can display... (4 Replies)
Discussion started by: oxoxo
4 Replies
4. UNIX for Dummies Questions & Answers
hey guys,
i've tried countless times to do this and have come up with:
find / type -f ".bashrc" -exec grep PS1 '{}' \; 2>/dev/null | ls -l
which tells bash:
find all the files in the system with the name .bashrc and look for modifcations to PS1 and terminate and rediret error msgs... (8 Replies)
Discussion started by: oxoxo
8 Replies
5. Shell Programming and Scripting
i have made a few changes to my bashrc file...have set a few environmental variable that my shell scripts use. Is there any way that these changes can reflect in evryone else's bashrc who are in the network or do all of them have to copy those changes to their own bashrc file. (2 Replies)
Discussion started by: lassimanji
2 Replies
6. Shell Programming and Scripting
Hi experts,
I am using bash shell and I cant find any .bashrc file in my home dir. Can anybody please help me out here....
If .bashrc file is not there, from where my shell config operates? Also I want to set my prompt like...
$
Please advice. (5 Replies)
Discussion started by: gentleDean
5 Replies
7. Shell Programming and Scripting
I am trying to do some changes at bashrc file located at /etc directory of my server. First I tried to edit bashrc via FTP downloaded on my pc changed it and loaded back, but it seems like changes are not reflecting.
Therefore I tried to change it via putty shel using vim bashrc command. but... (4 Replies)
Discussion started by: ninadgac
4 Replies
8. Homework & Coursework Questions
1.) I am to write scripts that will be phasetest folder in the home directory.
2.) The folder should have a set-up,phase and display files
I have written a small script which i used to check for the existing users and their password.
What I need help with:
I have a set of questions in a... (19 Replies)
Discussion started by: moraks007
19 Replies
9. UNIX for Advanced & Expert Users
Could someone please tell me how to unset your .bashrc? I have tried all of these. I can't find anything useful from google.
unset -f .bashrc
unset .bashrc (9 Replies)
Discussion started by: cokedude
9 Replies
10. Shell Programming and Scripting
I have modified the .bashrc. The problem is that when I write a long command,
it does not write on the next line but continues to write on the same line.
# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for... (1 Reply)
Discussion started by: kristinu
1 Replies
command(1) General Commands Manual command(1)
NAME
command - Treats command arguments as simple commands
SYNOPSIS
command [-p] command_name [argument...]
command [-v | -V] command_name
The command command causes the shell to treat the arguments to command as simple commands, and suppresses the default shell function
lookup.
STANDARDS
Interfaces documented on this reference page conform to industry standards as follows:
command: XCU5.0
Refer to the standards(5) reference page for more information about industry standards and associated tags.
OPTIONS
Performs the command search using a default value for PATH that is guaranteed to find all of the standard utilities. Writes a string to
standard output that indicates the path name or command to be used by the shell in the current shell execution environment to invoke com-
mand_name. Writes a string to standard output that indicates how the name given in the command_name operand will be interpreted by the
shell in the current shell execution environment.
DESCRIPTION
The command command allows you to run the following commands: User-defined commands whose names correspond to shell built-in commands.
System commands whose names correspond to shell built-in commands.
The command_name argument specifies the name of a utility. The one or more optional arguments to command_name specify strings treated as
arguments to the specified utility. It also provides information concerning how a command name will be interpreted by the shell.
NOTES
[Tru64 UNIX] If command_name is not the name of a function, the effect of command is the same as would be obtained by specifying com-
mand_name without command.
RESTRICTIONS
Since the -v and -V options to command produce output in relation to the current shell execution environment, if command is called in a
subshell or separate utility execution environment, it may not produce correct results. The following are examples of this type of opera-
tion:
(PATH=foo command -v) nohup command -v
EXIT STATUS
When the -v or -V options are specified, command returns one of the following values. Successful completion. The command_name could not
be found, or an error occurred.
If the -v or -V options are not specified, command returns one of the following values on error. The utility specified by command_name was
found but could not be invoked. An error occurred in the command command, or the utility specified by the command_name argument could not
be invoked.
If no error occurs, the exit status of command is that of the command specified by the arguments to command.
EXAMPLES
To ensure execution of the simple command pwd instead of the pwd shell built-in command, enter the following: command -p pwd
The preceding command displays the full path name of the current directory, and does not perpetuate a view of the current directory loca-
tion created by links as the shell built-in command might do.
ENVIRONMENT VARIABLES
The following environment variables affect the execution of command: Provides a default value for the internationalization variables that
are unset or null. If LANG is unset or null, the corresponding value from the default locale is used. If any of the internationalization
variables contains an invalid setting, the utility behaves as if none of the variables had been defined. If set to a non-empty string
value, overrides the values of all the other internationalization variables. Determines the locale for the interpretation of sequences of
bytes of text data as characters (for example, single-byte as opposed to multibyte characters in arguments). Determines the locale that
should be used to affect the format and contents of diagnostic messages written to standard error. Determines the location of message cat-
alogues for the processing of LC_MESSAGES. Determines the search path used during the command search unless the -p option is specified.
SEE ALSO
Commands: env(1), hash(1), type(1)
Standards: standards(5)
command(1)