08-03-2010
You can add path=$PATH:/opt/local/share/nwchem/nwchem in ~/.bash_profile
then you have two choice:
1 source ~/.bash_profile
so ,you can use your command now.
2 log out and then log in
then you can find it works
Last edited by skles; 08-03-2010 at 02:56 AM..
Reason: typo
10 More Discussions You Might Find Interesting
1. Programming
Hello all,
i've written a small piece of code that will read commands from standard input and executes the commands.
Its working fine and is execting the commands well. Accepting arguments too. e.g
#mkdir <name of the directory>
The problem is that its not letting me change the directory i.e... (4 Replies)
Discussion started by: Phrozen Smoke
4 Replies
2. Shell Programming and Scripting
hi,
i have a script that runs on bash and would like to run it on a machine that has csh and bash. the default setting on that machine is csh. i dont want to change my code to run it with a csh shell. is there any way i can run the script (written in bash) on this machine? in other words is there... (3 Replies)
Discussion started by: npatwardhan
3 Replies
3. Shell Programming and Scripting
I want to write a script which would run from one host say A and connect to other remote host B and then run rest of commands in that host. I tried connecting from A host to B with SSH but after connecting to host B it just getting me inside Host B command prompt. Rest of the script is not running... (6 Replies)
Discussion started by: SN2009
6 Replies
4. Shell Programming and Scripting
Hi,
please advise a script, something like this:
If ;
then
do something
else ( or for any other day of the week )
do otherthing
fi
Thanks (5 Replies)
Discussion started by: fed.linuxgossip
5 Replies
5. Shell Programming and Scripting
Is it possible to store all standard-out of a bash script and the binaries it calls in a log file AND still display the stdout on screen?
I know this is possible to store ALL stdout/stderr of a script to a single log file like:
exec 1>&${logFile}
exec 2>&1
But running a script with the... (3 Replies)
Discussion started by: ckmehta
3 Replies
6. Shell Programming and Scripting
Hi all. On X11 I'm on a shell ...shell_1 (/bin/bash). From here I want to open another shell window shell_2 who executes commands like "ls -l" or programs like ". /program"... so the "result" of commands shows in shell_2 window and not in shell_1. Is that possible ? (4 Replies)
Discussion started by: jerold
4 Replies
7. Shell Programming and Scripting
Hi to all,
i have the following problem...
i want to run three commands in a script in different shells... the first command is running always and is needed for the second on to run properly... example
# Procedure 1
xterm -e exec1 arg1 arg2
# Procedure 2
xterm -e exec2 arg1 arg2
#... (6 Replies)
Discussion started by: paladinaeon
6 Replies
8. IP Networking
Hi,
i used this tutorial which tells me to use following example command to proxify traffic from my linux
export {http,https,ftp}_proxy=122.228.156.126:80
when i do this command from command line it works and then i curl http://site/ipcheck.php i see its proxified, which is what i want to... (5 Replies)
Discussion started by: postcd
5 Replies
9. Shell Programming and Scripting
How to run several bash commands put in bash command line without needing and requiring a script file.
Because I'm actually a windows guy and new here so for illustration is sort of :
$ bash "echo ${PATH} & echo have a nice day!"
will do output, for example:... (4 Replies)
Discussion started by: abdulbadii
4 Replies
10. Solaris
I use plink.exe to automate remote commands that return data to Windows machines. This works well on newer servers running Red Hat since the commands were developed for bash and the designated user's login shell is bash. I need to also support older servers which are running Solaris 10 but the... (5 Replies)
Discussion started by: randman1
5 Replies
LEARN ABOUT MOJAVE
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.
--shallow-since=<date>
Deepen or shorten the history of a shallow'repository to include all reachable commits after <date>.
--shallow-exclude=<revision>
Deepen or shorten the history of a shallow repository to exclude commits reachable from a specified remote branch or tag. This option
can be specified multiple times.
--deepen-relative
Argument --depth specifies the number of commits from the current shallow boundary instead of from the tip of each remote branch
history.
--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.
If the remote has enabled the options uploadpack.allowTipSHA1InWant, uploadpack.allowReachableSHA1InWant, or
uploadpack.allowAnySHA1InWant, they may alternatively be 40-hex sha1s present on the remote.
SEE ALSO
git-fetch(1)
GIT
Part of the git(1) suite
Git 2.17.1 10/05/2018 GIT-FETCH-PACK(1)