05-23-2013
dos2unix: perl -npi -e 's/\r$//'
unix2dos: perl -npi -e 's/$/\r/'
10 More Discussions You Might Find Interesting
1. AIX
Hello again,
I would like to know if the following commands:
diag, errpt, lscfg, lspv, lsvg, lsps, lslv for AIX and
prtdiag, psrinfo, sysdef for SUN are native to these systems or if they are in fact scripts that are added after the unix installation.
Thank you in advance.
Have a nice day (4 Replies)
Discussion started by: VeroL
4 Replies
2. Solaris
hi,
is there any library functions available in sun solaries for encryption and decryption functions.
regards
suresh (1 Reply)
Discussion started by: suresh_rtp
1 Replies
3. UNIX for Dummies Questions & Answers
Hi,
I'm puzzled at how this could be.
I'm trying to transfer some files from an Sun box to an AIX box via FTP. The file transfer goes fine until it reaches a file of about 150k then times out and fails.
The FTP Does not seem to be able to transfer files of more than 150k! However, I can... (5 Replies)
Discussion started by: bbbngowc
5 Replies
4. AIX
Hi All,
We are in the processing of upgrading our AIX server OS from 5.2.0.0 to 6.1. And we have a set of highly critical running C applications in AIX box. I have a question like whether this upgradation of OS will affect any C code compilation and C runtime enviornment...
how does AIX 6.1... (1 Reply)
Discussion started by: karthikc
1 Replies
5. Solaris
Hi guru
I want to know which company's hardware is more stable means in term of H/W faults or replacement, in case of IBM (AIX), HP (HPUX) & SUN MICROSYSTEM (Solaris) & which order also, if we go through more stable to less stable system.
Regards (1 Reply)
Discussion started by: girish.batra
1 Replies
6. UNIX for Dummies Questions & Answers
AIX & DB2 paging issues
Hello I needs some help on AIX & DB2 paging issues. Recently a db2 query caused paging issues which then lead to memory problems and a server restart. Is there anyway of finding out what db2 queries were causing the problem..
Thanks in advance (2 Replies)
Discussion started by: nedkao
2 Replies
7. UNIX for Advanced & Expert Users
I need to capture lengthy screen puts and direct to .txt.
Script command is started on Wed Aug 22 13:27:36 EDT 2012.
# qcp
sh: qcp: not found.
An issue I have is that script command doesn't take non-AIX commands.
I need to run application-specific commands and capture the output in... (2 Replies)
Discussion started by: Daniel Gate
2 Replies
8. Red Hat
Hi All,
The scripts developed in AIX can be executed in Red Hat Linux too? Because, we are migrating OS from AIX to LINUX.
Will there be any differences in commands?
Thanks in advance!!!
Regards,
U (2 Replies)
Discussion started by: unme
2 Replies
9. Shell Programming and Scripting
Firstly, I would like to apologize if this is not the appropriate sub-forum to post about GNU/BSD makefile scripting. Though my code is in C++, because I am focusing on the makefile I thought it would go better in shell scripting. Please correct me if I am wrong.
Secondly, I am not interested in... (0 Replies)
Discussion started by: AntumDeluge
0 Replies
10. Shell Programming and Scripting
We have a lot of scripts using cut as :
cut -c 0-8 --works for cut (GNU coreutils) 5.97, but does not work for cut (GNU coreutils) 8.4.
Gives error -
cut: fields and positions are numbered from 1
Try `cut --help' for more information.
The position needs to start with 1 for later... (6 Replies)
Discussion started by: Vikram Jain
6 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)