05-04-2007
Quote:
Originally Posted by jim mcnamara
HPUX 11.23 does not have this problem - I just checked - I was using 11.0.
I am assuming it is a bug.
You might try loading the latest 11.0 sed patch and libc patch to see if that fixes it.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi there, I've an stupid question. If I make a telnet to a server from my computer and then execute a command that starts an application (on the server), when I disconnect, the application stops running, which is pretty obvious. Is it possible to add a flag at the end of the command so when I cut... (4 Replies)
Discussion started by: piltrafa
4 Replies
2. Programming
I put this here because it is a 'behavior' type question..
I seem to remember doing ls .* and getting all the .-files, like
.profile
.login
etc.
But ls .* doesn't do that, it lsts the contents of every .*-type subdirectory.
Is it supposed to?
I should think that a -R should be given to... (10 Replies)
Discussion started by: AtleRamsli
10 Replies
3. UNIX for Dummies Questions & Answers
I have a file called products.kp which contains, for example,
12345678,1^M
87654321,2^M
13579123,3
when I run the command
cat products.kp| sed -f kp.sed
where kp.sed contains
s,^M,,
I get the output
12345678,1
87654321,2
13579123,3 (5 Replies)
Discussion started by: Kevin Pryke
5 Replies
4. Programming
Hi All,
I ve written a small program to get started off with pthreads. I somehow feel the program doesnt meet the purpose. Please find the code and the output below. Please find my question at the bottom.
#include <pthread.h>
#include <stdio.h>
#include <stdlib.h>
void *PrintThread1(void... (4 Replies)
Discussion started by: nhrraj
4 Replies
5. HP-UX
I am working with the following code:
#include <stdlib.h>
#include <string>
#include <iostream>
using std::cout;
using std::endl;
using std::flush;
int main()
{
long lng1 = 123;
long lng2 = 4567;
cout<<ltoa(lng1)<<ltoa(lng2)<<endl<<flush;
return 0;
}
Instead of receiving... (2 Replies)
Discussion started by: charitonca
2 Replies
6. Shell Programming and Scripting
Echo is removing extra blank spaces. See the command.
export INSTALLDIR=”First Second /Two Space”
echo $INSTALLDIR
out put: First Second /Two Space
Here only on blnak space is present while with command
Echo “$INSTALLDIR”
Out put: ”First Second /Two Space”
It's correct output... (2 Replies)
Discussion started by: Saurabh78
2 Replies
7. Shell Programming and Scripting
Hi all,
I have one question regarding sed regexp (or any regexp in general),
I have some path like this
C:/Abc/def/ghi/jkl in a file file1
Now if i use following code
cat file1 | sed 's#\(.*\)/.*#\1#'
Now it give me following output
C:/Abc/def/ghi, which is fine
But i just... (2 Replies)
Discussion started by: sarbjit
2 Replies
8. Shell Programming and Scripting
Hi gurus
input file:
1
2
3
4
desired output
1
2\
2a
3
4
I tried (6 Replies)
Discussion started by: wakatana
6 Replies
9. Programming
I have the following program:
int main(int argc, char** argv){
unsigned long int mean=0;
for(int i=1;i<10;i++){
mean+=poisson(12);
cout<<mean<<endl;
}
cout<<"Sum of poisson: "<< mean;
return 0;
}
when I run it, I get the... (4 Replies)
Discussion started by: santiagorf
4 Replies
10. HP-UX
Our comp-operator has come across a peculiar ‘feature'. We have this directory where we save all the reports that were generated for a particular department for only one calendar year. Currently there are 45,869 files. When the operator tried to backup that drive it started to print a flie-listing... (3 Replies)
Discussion started by: vslewis
3 Replies
LEARN ABOUT LINUX
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)