06-01-2009
Unavailable/Slow Network Paths in $PATH
At work, I'm in a Solaris environment working with csh, and $PATH is populated with anywhere between 10 and 20 entries.
Last week, every command I issued (even "ls") took several seconds, if not an entire minute, to run. Once I moved "/home/sybase/bin" to the end of $PATH, certain commands started working immediately. Still, other commands such as "vim" still take forever. I want to find out what is causing the slow-down.
How can I check, or somehow "ping" each path in $PATH? (Given one example, I can easily write a script, but I'm not sure how to get started.)
Thank you.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello, everyone:
i encounter a problem these days , pls help me ,thanks in advance.
my env:
machine: ES40 A ES40 B
os: true64 Unix 4.0f
note: src.tar 8M network card speed 100M
my problem:
... (3 Replies)
Discussion started by: q30
3 Replies
2. Solaris
Hi all,
I downloaded a tarball of coreutils ....
extracted only to find out that i had to build it...
But when i executed ./configure, this is what i got
checking build system type... i386-pc-solaris2.11
checking host system type... i386-pc-solaris2.11
configure: autobuild project... GNU... (2 Replies)
Discussion started by: wrapster
2 Replies
3. Shell Programming and Scripting
After installation of FreeBSD there are post installation activities to be executed through a script. Since these activities are dependent upon a network being available, I want the script to detect whether a network connection is present or else halt the script. I currently have this test:
#... (2 Replies)
Discussion started by: figaro
2 Replies
4. Red Hat
hey guys,
We have two Sun x2100 servers running RHEL5 in a test environment. Both servers are fresh OS installs and hooked up to the same network switch.
When ssh'ing to one server, there is a significant delay, while ssh'ing to the other server, the connection is almost instant. We are... (2 Replies)
Discussion started by: amheck
2 Replies
5. BSD
There is a FreeBSD machine which normally has a network connection, but after a recent start up no longer has such a connection. All other computers on the same router do have an active network. Where do I start looking to troubleshoot this?
Thanks in advance (2 Replies)
Discussion started by: figaro
2 Replies
6. Solaris
Hi,
One of our Solaris servers was peviously zoned and connected to 2 seperate arrays, one HP and the other EMC. The server is now only connected to the EMC. The sever has x2 single port HBA's.
When running cfgadm I see the following:
root@qwicprod /dev/rdsk]# cfgadm -al
Ap_Id Type... (6 Replies)
Discussion started by: jamba1
6 Replies
7. UNIX for Advanced & Expert Users
Solaris 10 Server refuse to connect :wall:
fork: Resource temporarily unavailable , server unexpectedly unavailable network connection , refuse error, disconnect message, fatal error type2, (protocol error type2)
Issue has been resolved after taken few steps :b:
First of all need to check... (1 Reply)
Discussion started by: taherahmed
1 Replies
8. UNIX for Dummies Questions & Answers
Hi - I am trying to include the MSQ.exe that I have downloaded for the sake of learning. My current /.bash_profile file reads:
PATH=/Library/Frameworks/Python.framework/Versions/3.1/bin:/Applications/XAMPP/xamppfiles/bin:$PATH
export PATH
-----------------------------------
... (4 Replies)
Discussion started by: Alexander4444
4 Replies
9. Red Hat
Hi,
I have 2 machines in production environment:
1. redhat machine for application
2. DB machine (oracle)
The application doing a lot of small read&writes from and to the DB machine.
The problem is that after some few hours the network from the application to the DB becomes very slow and... (4 Replies)
Discussion started by: moshesa
4 Replies
10. AIX
Hello everyone,
I've been a life long Unix/Linux user but I'll be the first to admit I have little specific AIX knowledge at this point and I've inherited these systems for better or worse so please forgive if I ask something in the wrong context. And yes, I've searched google for 3 days now :)... (3 Replies)
Discussion started by: BDMcGrew
3 Replies
LEARN ABOUT NETBSD
npm-run-script
NPM-RUN-SCRIPT(1) NPM-RUN-SCRIPT(1)
NAME
npm-run-script - Run arbitrary package scripts
SYNOPSIS
npm run-script <command> [--silent] [-- <args>...]
alias: npm run
DESCRIPTION
This runs an arbitrary command from a package's "scripts" object. If no "command" is provided, it will list the available scripts.
run[-script] is used by the test, start, restart, and stop commands, but can be called directly, as well. When the scripts in the package
are printed out, they're separated into lifecycle (test, start, restart) and directly-run scripts.
As of ` https://blog.npmjs.org/post/98131109725/npm-2-0-0, you can use custom arguments when executing scripts. The special option -- is
used by getopt https://goo.gl/KxMmtG to delimit the end of the options. npm will pass all the arguments after the -- directly to your
script:
npm run test -- --grep="pattern"
The arguments will only be passed to the script specified after npm run and not to any pre or post script.
The env script is a special built-in command that can be used to list environment variables that will be available to the script at run-
time. If an "env" command is defined in your package, it will take precedence over the built-in.
In addition to the shell's pre-existing PATH, npm run adds node_modules/.bin to the PATH provided to scripts. Any binaries provided by
locally-installed dependencies can be used without the node_modules/.bin prefix. For example, if there is a devDependency on tap in your
package, you should write:
"scripts": {"test": "tap test/*.js"}
instead of
"scripts": {"test": "node_modules/.bin/tap test/*.js"}
to run your tests.
The actual shell your script is run within is platform dependent. By default, on Unix-like systems it is the /bin/sh command, on Windows it
is the cmd.exe. The actual shell referred to by /bin/sh also depends on the system. As of `
https://github.com/npm/npm/releases/tag/v5.1.0 you can customize the shell with the script-shell configuration.
Scripts are run from the root of the module, regardless of what your current working directory is when you call npm run. If you want your
script to use different behavior based on what subdirectory you're in, you can use the INIT_CWD environment variable, which holds the full
path you were in when you ran npm run.
npm run sets the NODE environment variable to the node executable with which npm is executed. Also, if the --scripts-prepend-node-path is
passed, the directory within which node resides is added to the PATH. If --scripts-prepend-node-path=auto is passed (which has been the
default in npm v3), this is only performed when that node executable is not found in the PATH.
If you try to run a script without having a node_modules directory and it fails, you will be given a warning to run npm install, just in
case you've forgotten.
You can use the --silent flag to prevent showing npm ERR! output on error.
You can use the --if-present flag to avoid exiting with a non-zero exit code when the script is undefined. This lets you run potentially
undefined scripts without breaking the execution chain.
SEE ALSO
o npm help 7 scripts
o npm help test
o npm help start
o npm help restart
o npm help stop
o npm help 7 config
January 2019 NPM-RUN-SCRIPT(1)