|
|
Sponsored Content
Top Forums
Shell Programming and Scripting
C Shell path variable causing very slow shell!?HELP
Post 302536835 by vas28r13 on Thursday 7th of July 2011 09:21:05 AM
07-07-2011
C Shell path variable causing very slow shell!?HELP
I am using C Shell MKS Toolkit and I ran into a huge problem when setting up some environment variables.
The csh script that I have as my login script runs fine but very very slow.
When I add a directory to my PATH it seems to slow down shell startup and even slow down the commands.
It is one path directory that is causing me all the problems. The path directory does indeed contain a lot of scipts and files, so I do understand its not going to be as fast, but it slows down the shell way too much. When running the scripts as commands from the directory, it takes around 5-10 seconds when it should be split second commands/scritps. For example, if I put the full path of where the script then its fast. If I rely on the path variables then it takes over 5 seconds!
And to start my shell using the script at login takes around 30 seconds!
I hear that path hashing is something that can be the problem fom me since there is one path variable that contains hundreds of files and scripts. I think it would be better without path hashing.
The 'unhash' command does not seem to be doing anything. How can that be??? there is no change in time and hashstat still gives me some numbers at the end. anyone know how I can make sure I turn off path hashing and the use of the internal hashtable??
I don't see how there is no change when using 'unhash'
OK, so perhaps the startup of the shell can be slow, but why is running commands so slow also? I understand the path that contains the command script has a lot of directories, files and scipts but I hear that it should not slow down the shell that significantly.
Anyone run into this problem? or have any suggestions. Anything will be appreciated. Thank you!
Also..how come I always see in examples path variables in the form of something like /somefolder/somefolder but MKS seems to only recognize full paths like drive:/somefolder/somefolder/somefold???
---------- Post updated 07-07-11 at 09:21 AM ---------- Previous update was 07-06-11 at 10:37 AM ----------
Sorry for double posting, but let me ask some simpler questions that will help me..
when I add a PATH variable, sar for example c:/somefolder, do all the directories in c:/somefolder also get referenced?
can anyone explain the 'unhash' command and how they implemented it. I used it in my script but didn't seem to disable the internal hash table lookup.
The csh script that I have as my login script runs fine but very very slow.
When I add a directory to my PATH it seems to slow down shell startup and even slow down the commands.
It is one path directory that is causing me all the problems. The path directory does indeed contain a lot of scipts and files, so I do understand its not going to be as fast, but it slows down the shell way too much. When running the scripts as commands from the directory, it takes around 5-10 seconds when it should be split second commands/scritps. For example, if I put the full path of where the script then its fast. If I rely on the path variables then it takes over 5 seconds!
And to start my shell using the script at login takes around 30 seconds! I hear that path hashing is something that can be the problem fom me since there is one path variable that contains hundreds of files and scripts. I think it would be better without path hashing.
The 'unhash' command does not seem to be doing anything. How can that be??? there is no change in time and hashstat still gives me some numbers at the end. anyone know how I can make sure I turn off path hashing and the use of the internal hashtable??
I don't see how there is no change when using 'unhash'
OK, so perhaps the startup of the shell can be slow, but why is running commands so slow also? I understand the path that contains the command script has a lot of directories, files and scipts but I hear that it should not slow down the shell that significantly.
Anyone run into this problem? or have any suggestions. Anything will be appreciated. Thank you!
Also..how come I always see in examples path variables in the form of something like /somefolder/somefolder but MKS seems to only recognize full paths like drive:/somefolder/somefolder/somefold???
---------- Post updated 07-07-11 at 09:21 AM ---------- Previous update was 07-06-11 at 10:37 AM ----------
Sorry for double posting, but let me ask some simpler questions that will help me..
when I add a PATH variable, sar for example c:/somefolder, do all the directories in c:/somefolder also get referenced?
can anyone explain the 'unhash' command and how they implemented it. I used it in my script but didn't seem to disable the internal hash table lookup.
|
|
8 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I set my path environment variable in c shell, using the
syntax below
setenv PATH "${PATH}:/usr/local:/usr/local/bin"
and placed this in $HOME/.login
$HOME/.cshrc
and /etc/.login
/etc/.cshrc
but when I issued echo $PATH or set command
the output does not reflect changes made to... (5 Replies)
Discussion started by: hassan2
5 Replies
2. Shell Programming and Scripting
hi all
i have joined new to the group.
i have set an variable in my bashrc file.
.bashrc
PROGHOME=/home/braf/braf/prog
export PROGHOME
but while using it in my shell script its path is not taken and i had to explicitly give the export command to set the path.
in my script... (8 Replies)
Discussion started by: krithika
8 Replies
3. Shell Programming and Scripting
Hi!
1. I have a parameter file containing path to log files. For this example both paths are the same, one is stated directly and the second using env variables.
/oracle/admin/orcl/bdump/:atlas:trc:N
${ORACLE_BASE}/admin/${ORACLE_SID}/bdump/:${ORACLE_SID}:trc:N
2. I try to parse the path... (1 Reply)
Discussion started by: lojzev
1 Replies
4. Shell Programming and Scripting
Hi,
I am new to shell scripting.I tried adding an entry to the path variable like below
export PATH=$PATH:/opt/xxx/bin
But am getting an error invalid identifier /opt/xxx/bin
Can someone tell me the error above and correct me .
Thanks and Regards,
Padmini (2 Replies)
Discussion started by: padmisri
2 Replies
5. Shell Programming and Scripting
Hi all!
I have written a shell script which will invoke perl script infinitly in the background in a loop. Code will do as:Within while loop, perl script will be run in background, get the pid and notify pid in though mail. then wait for pid to be completed before going for next iteration. I am... (1 Reply)
Discussion started by: jramesh1
1 Replies
6. UNIX for Dummies Questions & Answers
I've created a test script, which is located in $HOME/bin. The script runs as expected with no issues. However, upon echo'ing the $path variable the location of my script is not located in any of the directories listed in $path. So my question is, how does shell know where the script is located... (2 Replies)
Discussion started by: BrandonD
2 Replies
7. Shell Programming and Scripting
I have shell program as below
#!/bin/sh
echo ======= LogManageri start ==========
#This directory is getting the raw data from remote server
Raw_data=/opt/ftplogs
# This directory is ready for process the data
Processing_dir=/opt/processing_dir
# This directory is prcoessed files and... (4 Replies)
Discussion started by: Chenchireddy
4 Replies
8. UNIX for Beginners Questions & Answers
So I created two shell variables: COLUMN1_HEADING, COLUMN2_HEADING.
They have values:
COLUMN1_HEADING="John"
COLUMN2_HEADING="123456789"
How would I use printf to get it to print an output like this: $COLUMN1_HEADING\t$COLUMN2_HEADING\nJohn\t123456789\n
Thanks! (3 Replies)
Discussion started by: steezuschrist96
3 Replies
LEARN ABOUT OPENSOLARIS
use
USE(1) User Commands USE(1) NAME
use - Frontend to the Usepackage Environment Manager SYNOPSIS
csh and derivatives: source /usr/share/usepackage/use.csh bourne shell and derivatives: source /usr/share/usepackage/use.bsh korn shell: . /usr/share/usepackage/use.ksh use [-vs] [-f file] package ... use -l DESCRIPTION
Usepackage is an environment management program. It is based on the principle of packages - collections of executables that share a common set of necessary environment variables, such as PATH, MANPATH or LD_LIBRARY_PATH. For each given package, use sources the appropriate environment information into the current shell. The environment information is speci- fied in a configuration file, see usepackage(1). OPTIONS -v Output verbose information to the standard error stream. -s Silence warnings for un-matched packages. This is useful in a shell rc script when a package is known not to be available on all architectures that the shell is used on. -f file Specify an alternate initial configuration file. -l List available packages and groups. FILES
/usr/share/usepackage/usepackage.conf The default configuration file. /usr/share/usepackage/use.csh Shell setup for csh and derivatives. /usr/share/usepackage/use.bsh Shell setup for bourne shell and derivatives. /usr/share/usepackage/use.ksh Shell setup for ksh. /usr/bin/usepackage The underlying Usepackage executable. ENVIRONMENT
Other than the reading and re-definition of environment variables for package setup, use also uses the following environment variables for user configuration: PACKAGES_PATH Colon-separated path list giving the directories to search for configuration files. Shell-style tilde (~) user-directory escapes are expanded. HOME If present in the environment, this is used to provide the expansion for the tilde (~) user-directory. SHELL If present in the environment, the last path component of this is used for shell matching (see SYNTAX) and detecting the style of environment output that should be used, see usepackage(1). COPYRIGHT
Usepackage Environment Manager Copyright (C) 1995-2005 Jonathan Hogg This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MER- CHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA SEE ALSO
usepackage(1), csh(1), sh(1), ksh(1) Usepackage $Date: 2005/12/11 16:42:09 $ USE(1)