10-16-2012
How to add path to root user
i tried to find .bash_profile file home directory.
i can see only .bashrc file will be there.
in .bashrc file can we add path for root?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
i mistyped the location of bash and now i can't login as the only other user who belongs to wheel on my freebsd box.
since i'm having many problems with samba, this has frozen my attempts to get things resolved with the former issue.
i've been told that 'su -m' should do the trick, but it's... (3 Replies)
Discussion started by: xyyz
3 Replies
2. Shell Programming and Scripting
Hi:
I have a requirement as below:
I have some standard Unix commands modified and kept them in a directory say /usr/clsh/bin. For example I have a script named "ls" kept here which is modified version of "ls" (say it always gives long listing i.e. ls -l).
When any user logs on and types... (2 Replies)
Discussion started by: ramesh_samane
2 Replies
3. Shell Programming and Scripting
Hi All
I have written one shell script for GPRS route add is given below named GPRSRouteSet.sh
URL="www.google.com"
VBURL="10.5.2.211"
echo "Setting route for $URL for GPRS"
URL_Address=`nslookup $URL|grep Address:|grep -v "#"|awk -F " " '{print $2}'|head -1`
echo "Executing ... (3 Replies)
Discussion started by: mnmonu
3 Replies
4. UNIX for Dummies Questions & Answers
hi
i am new to unix and i have abig task. i have to \run particular commands having root privileges from a non root user. i know sudo is one of the way but i need sum other approach kindly help
Thanks (5 Replies)
Discussion started by: suryashikha
5 Replies
5. Shell Programming and Scripting
Hello Folks,
I want to append a path in user's PATH variable which should be available in current session.
Background
Numerous persons will run a utility.
Aim is to add the absolute path of the utility the first time it runs so that next runs have the PATH in env & users can directly run... (6 Replies)
Discussion started by: vibhor_agarwali
6 Replies
6. Solaris
hi All, here is the problem: I'm not able to specify a PATH inside the user crontab file (/var/spool/cron/crontabs). The only syntax it accepts is the usual "* * * * * file" I'm not able to add PATH, or HOME, or MAILTO, or anything else. when I try to save the crontab, I have the error: ... (1 Reply)
Discussion started by: joe_x
1 Replies
7. Solaris
Sorry this maybe a dumb one, but I am root and want to add something to my PATH.
Is the right place to do it here:
/usr/dt/config/dtspcdenv ?
If so, after I add it, how do I source it? Neither
"source <file>" nor ". <file>" work.
How does the above file work... is there another... (5 Replies)
Discussion started by: steve701
5 Replies
8. UNIX for Dummies Questions & Answers
I've been through many threads before i decide to create a separate thread.
I can't really find the solution to my (simple) problem.
Here's what I'm trying to achieve:
As "canar" user I want to run a command, let's say "/opt/ocaml/bin/ocaml" as "duck" user.
The only to achieve this is to... (1 Reply)
Discussion started by: canar
1 Replies
9. UNIX for Advanced & Expert Users
Hi!! one strange problem occurred with my RHEL 5 box.
i'm having logs folder with ownership of non-root user. Created some files with root user under logs folder.
here is the scene:
-rw-r----- 1 root root 1048227 Feb 28 12:34 SystemOut_13.02.28_12.34.10.log
-rw-r----- 1 root root ... (6 Replies)
Discussion started by: sukhdip
6 Replies
10. Shell Programming and Scripting
Currently in my system Red Hat is installed. And Many user connect to my machine via SSH Techia Terminal.
I want to give some users a root level access.
Can anyone please help me how to make it possible. I too searched on the Google but didn't find the correct way
Regards
ADI (4 Replies)
Discussion started by: adisky123
4 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)