05-27-2009
CD (change directory) - Not advisable for executing a command
Hi,
This is a quick one.
I have got a review comment in one of the scripts that i wrote:
"In UNIX script it not advisable to use cd to a directory and then run command."
Is this true?
I was trying to cd to log directory and use some cat or head or ls command.
Many Thanks,
Sam
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I want to limit the directories that a user can
access. When this users logs in, I do not want
them to cd to any directory but those in their
$HOME. In other words:
login:
pwd:
/home/user
cd / -- user tries to cd to root directory.
pwd
/home/user -- user is still in home... (4 Replies)
Discussion started by: oscarr
4 Replies
2. Shell Programming and Scripting
Hi Guys.
I am a complete shell scripting newbie with some syntax and commands understanding. I'm more of a win admin. With that said: I need to write a shell script to monitor a directory '/Mon_Dir' for new occurrences of files with .xx extension. Once a new file is detected in the directory, a... (4 Replies)
Discussion started by: krkan
4 Replies
3. Shell Programming and Scripting
I have a shell script /home/user1/bin/sh1, how can I print out the directory of this file inside the script.
Say I am in /home/user1/, then I run
/home/user1/bin/sh1
I need it to print out /home/user1/bin.
Thanks. (2 Replies)
Discussion started by: jasony001
2 Replies
4. Shell Programming and Scripting
What's wrong with this script?????
Please help!!!
!#/bin/sh
echo "please enter dir"
read input
cd $input
I'm trying to make a simple script to change dir. But does not work.
it stays at the same dir where i run the script.
What did i do wrong?? (21 Replies)
Discussion started by: c00kie88
21 Replies
5. Shell Programming and Scripting
Hi all,
I am getting : No such file or directory while executing a shell script. But i have that corresponding file in the corresponding path. It also have executable rights. Please help me out in this
Thanks in advance.
Ananthi.U (7 Replies)
Discussion started by: ananthi_ku
7 Replies
6. Shell Programming and Scripting
hi,
I tried whence $0, but that just gives me the filename relative to where I am executing the script from. I need to get the full pathname.
thanks (19 Replies)
Discussion started by: JamesByars
19 Replies
7. Shell Programming and Scripting
I'm writing a simple menu script and I would like to output the whole script using background color: black AND foreground color:white. Meaning if the ssh terminal of a user is set to green for example, it will change to my desired color when menu script is executed. Once the script is exited, it... (1 Reply)
Discussion started by: lhareigh890
1 Replies
8. Shell Programming and Scripting
I am trying to do the following task :
export ENV=aaa
export ENV_PATH=$(cd /apps | ls | grep $ENV)
However, it's not working. What's the way to change to directory and search some file in that directory in single command
Please help. (2 Replies)
Discussion started by: saurau
2 Replies
9. UNIX for Dummies Questions & Answers
Is there a way to run the profile which is not in $HOME directory? then whats the command for that? (1 Reply)
Discussion started by: SKhan
1 Replies
10. Shell Programming and Scripting
I'm finally about to make the jump from PHP's mysql driver to the newer mysqli one using the mysqli converter tool.
The tool is called by this command line:
php /usr/share/nginx/html/rather/converter/cli.php -d -p ".php,.shtml,.inc" -u -b -v -w >> /tmp/convert.log
e.g. at the web root:... (2 Replies)
Discussion started by: dheian
2 Replies
diffmk(1) General Commands Manual diffmk(1)
NAME
diffmk - mark changes between two different versions of a file
SYNOPSIS
prevfile currfile markfile
DESCRIPTION
compares the previous version of a file with the current version and creates a file that includes ``change mark'' commands. prevfile is
the name of the previous version of the file and currfile is the name of the current version of the file. generates markfile which con-
tains all the lines of the currfile plus inserted formatter ``change mark'' requests. When markfile is formatted, changed or inserted text
is shown by a character at the right margin of each line. The position of deleted text is shown by a single
If the characters and are inappropriate, a copy of can be edited to change them because is a shell script.
EXTERNAL INFLUENCES
International Code Set Support
Single- and multi-byte character code sets are supported.
EXAMPLES
A typical command line for comparing two versions of an file and generating a file with the changes marked is:
can also be used to produce listings of C (or other) programs with changes marked. A typical command line for such use is:
where the file contains:
The request can specify a different line length, depending on the nature of the program being printed. The request is probably needed only
for C programs.
WARNINGS
Aesthetic considerations may dictate manual adjustment of some output.
does not differentiate between changes in text and changes in formatter request coding. Thus, file differences involving only formatting
changes (such as replacing with in a text source file) with no change in actual text can produce change marks.
Although unlikely, certain combinations of formatting requests can cause change marks to either disappear or to mark too much. Manual
intervention may be required because the subtleties of various formatting macro packages and preprocessors is beyond the scope of cannot
tolerate commands in its input (see tbl(1)), so any request that would appear inside a range is silently deleted. The script can be
changed if this action is inappropriate, or can be run on two files that have both been run through the preprocessor before any comparisons
are made.
uses and thus has the same limitations on file size and performance that may impose (see diff(1)). In particular the performance is non-
linear with the size of the file, and very large files (well over 1000 lines) may take extremely long to process. Breaking the file into
smaller pieces may be advisable.
also uses the ed(1) editor. If the file is too large for error messages may be embedded in the file. Again, breaking the file into
smaller pieces may be advisable.
SEE ALSO
diff(1), nroff(1).
diffmk(1)