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 LINUX
git-fetch-pack
GIT-FETCH-PACK(1) Git Manual GIT-FETCH-PACK(1)NAME
git-fetch-pack - Receive missing objects from another repository
SYNOPSIS
git fetch-pack [--all] [--quiet|-q] [--keep|-k] [--thin] [--include-tag]
[--upload-pack=<git-upload-pack>]
[--depth=<n>] [--no-progress]
[-v] <repository> [<refs>...]
DESCRIPTION
Usually you would want to use git fetch, which is a higher level wrapper of this command, instead.
Invokes git-upload-pack on a possibly remote repository and asks it to send objects missing from this repository, to update the named
heads. The list of commits available locally is found out by scanning the local refs/ hierarchy and sent to git-upload-pack running on the
other end.
This command degenerates to download everything to complete the asked refs from the remote side when the local side does not have a common
ancestor commit.
OPTIONS --all
Fetch all remote refs.
--stdin
Take the list of refs from stdin, one per line. If there are refs specified on the command line in addition to this option, then the
refs from stdin are processed after those on the command line.
If --stateless-rpc is specified together with this option then the list of refs must be in packet format (pkt-line). Each ref must be
in a separate packet, and the list must end with a flush packet.
-q, --quiet
Pass -q flag to git unpack-objects; this makes the cloning process less verbose.
-k, --keep
Do not invoke git unpack-objects on received data, but create a single packfile out of it instead, and store it in the object database.
If provided twice then the pack is locked against repacking.
--thin
Fetch a "thin" pack, which records objects in deltified form based on objects not included in the pack to reduce network traffic.
--include-tag
If the remote side supports it, annotated tags objects will be downloaded on the same connection as the other objects if the object the
tag references is downloaded. The caller must otherwise determine the tags this option made available.
--upload-pack=<git-upload-pack>
Use this to specify the path to git-upload-pack on the remote side, if is not found on your $PATH. Installations of sshd ignores the
user's environment setup scripts for login shells (e.g. .bash_profile) and your privately installed git may not be found on the system
default $PATH. Another workaround suggested is to set up your $PATH in ".bashrc", but this flag is for people who do not want to pay
the overhead for non-interactive shells by having a lean .bashrc file (they set most of the things up in .bash_profile).
--exec=<git-upload-pack>
Same as --upload-pack=<git-upload-pack>.
--depth=<n>
Limit fetching to ancestor-chains not longer than n. git-upload-pack treats the special depth 2147483647 as infinite even if there is
an ancestor-chain that long.
--no-progress
Do not show the progress.
--check-self-contained-and-connected
Output "connectivity-ok" if the received pack is self-contained and connected.
-v
Run verbosely.
<repository>
The URL to the remote repository.
<refs>...
The remote heads to update from. This is relative to $GIT_DIR (e.g. "HEAD", "refs/heads/master"). When unspecified, update from all
heads the remote side has.
SEE ALSO git-fetch(1)GIT
Part of the git(1) suite
Git 1.8.5.3 01/14/2014 GIT-FETCH-PACK(1)