10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
On linux i have the below command working fine.
grep -o '<name>.*</name>' deploy.tmp | sed 's/\(<name>\|<\/name>\)//g' deploy.tmp
But the same is failing on Solaris
uname -a
SunOS mymac 5.10 Generic_150400-23 sun4v sparc sun4v
Can you tell me how can i get it work on Solaris ?... (6 Replies)
Discussion started by: mohtashims
6 Replies
2. Solaris
Hi Guys,
I need grep package with -A option for Solaris 10,
Where can I download this from,
Please advise. (2 Replies)
Discussion started by: manalisharmabe
2 Replies
3. Shell Programming and Scripting
Am using the following grep to match a particular patter in grep.
grep xyz abc.txt
now while i run this command, if the pattern matched, am getting the line containing xyz
Output: xyz is doing some work
Now if i want the file name also along with my output, what should i do
Expected... (2 Replies)
Discussion started by: rituparna_gupta
2 Replies
4. UNIX for Dummies Questions & Answers
Can anyone explain this (i.e. why the 2nd grep does not find anything)?:
-bash-3.00$ cat tmp.log
sftp> chdir /home/test-dir
sftp> mget thosefiles*.txt
File "/home/test-dir/thosefiles*.txt" not found.
-bash-3.00$ grep "s*.txt" tmp.log
sftp> mget thosefiles*.txt
File... (4 Replies)
Discussion started by: dhebden
4 Replies
5. Solaris
Hi,
I am interested in knowing the grep optiojs availabel in solaris box, to get the grep results in one line from the log files. only the matched values need to be displayed.
I need ot find the values in a message where the search values will be in separate lines of the input.
like:... (10 Replies)
Discussion started by: sudha143
10 Replies
6. Shell Programming and Scripting
I am using the code below to grep through a list of files (TEMPFILE) and look for rsync, rdist, rsh, ftp, etc. in each file. Do a count of each, and output that to a logfile.
This works great in Linux, but not at all in Solaris because the EGREP -o option does not exist.
Anyone have an idea... (5 Replies)
Discussion started by: nitrobass24
5 Replies
7. UNIX for Dummies Questions & Answers
Hello
I am trying to grep all the processes having strings "rman" and "MRTP"
i.e
ps -ef|grep (rman and MRTP)
how can i achieve this
Thankyou (7 Replies)
Discussion started by: njafri
7 Replies
8. UNIX for Dummies Questions & Answers
Hi my unix friends,
How do I grep a word and next line with solaris 10.
tnx
Mehrdad
---------- Post updated at 03:17 PM ---------- Previous update was at 03:09 PM ----------
I found this one:
cat <file_name> | awk '/<seek_word>/ {print;getline;print}' (3 Replies)
Discussion started by: mehrdad68
3 Replies
9. Solaris
grep -e doesn't work in Soalris.
Same script with grep -e worked on AIX/HP/LINUX..
I would like to search a list of patterns on "log.txt" like ...
grep -e FATAL -e ERROR log.txt
I get the error message as
grep: illegal option -- e
Usage: grep -hblcnsviw pattern file . . . (3 Replies)
Discussion started by: jmkraja
3 Replies
10. UNIX for Dummies Questions & Answers
Hi all,
I have a problem when i grep for a particular field among all fhe files in the directory.
if i do an ls -l field *
i can find it.
however at the moment the number of files in the directory are close to 28000 and it returns an
ksh: /usr/bin/grep: arg list too long
Assuming i... (2 Replies)
Discussion started by: manualvin
2 Replies
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)