I think I really over thought this and wasn't very clear in what my requirements were.
I originally had two scripts that worked great, but I needed two cron jobs to do and used more disk space because I gunzipped the files into one location and then edited them with another script into yet another directory.
My goal was to gunzip and edit together to only one directory, combining the two scripts I was using previously.
I got stuck on passing a shell variable from one script and passing it into the sed script.
This is what I came up with, I would appreciate it if anyone has a better way to do this.
Thanks again for looking into this!
Here's what I have...
$ vi foo1
- open foo1 and work around for a while. I yank a few lines into a buffer and then :w to save.
Next I :e foo2 to open foo2 and paste my buffer. I :w to save, but I would like to then be able to go directly back into foo1 where I was before I opened foo2. ... (4 Replies)
i had heard that linux is open source.....which meant that i could edit it.
so how do i start out? i've already downloaded it. the name's "puppy linux".....someone please reply quick!!!
and by the way, may i know what shell scripting is? (15 Replies)
Hi, I am trying to edit sshd_config file through the vi editor.
logged on as a root.
when I try to write the file I get:
Read-only file, not written; use ! to override
when i type :w!, I get:
Error: etc/ssh/sshd_config Permission denied.
I want to change:
#PermitRootLogin no to yes
freeBDS... (6 Replies)
Hello Everyone,
I have a few files in a directory such as :
abc.xyz.txt1.gz
abc.xyz.txt2.gz
....
....
...
...
abd.xyz.txt100.gz
And I want uncompressed files such as:
abc.xyz.txt1
abc.xyz.txt2
....
...
.....
.... (1 Reply)
Hi ALL,
Am working with the gunzip command to zip all the old files having 10 days
am using the command
find . -name '*.log' -type f -mtime +10 -exec gunzip {} \;
am facing two issues
1.)it displays the files which are all older than a year
2.)when am trying to gunzip all the... (2 Replies)
Hi, sometimes one wants to edit files while still seeing output of earlier commands in terminal. I've found out that cat test && cat - >> test does the trick for displaying file content and adding lines but I believe I saw a much cooler command that was also able to erase lines from files. I cannot... (6 Replies)
I have compressed files under directory '/root/data' and i need the uncompressed files in another directory
'/root/uncom'. I running a shell script below shell script from directory '/root/'
gunzip /root/data/*.gz -d /root/uncom
But this is failing with
gunzip: /root/uncom is a directory... (2 Replies)
Hi all,
I have a directory with multiple (thousnads) of files, which are named this way
ABCDEF.wo.im-1
OKRAME.ire.roi
IOJEAFO01.irt.gfg
IMNYBL05.REG.gkf
I would like to keep the part of the name (everything before the first dot in the filename).
The desired output:
ABCDEF... (3 Replies)
I have compressed files under directory '/root/data' and i need the uncompressed files in another directory
'/root/uncom'. I running a shell script below shell script from directory '/root/'
gunzip /root/data/*.gz -d /root/uncom
But this is failing with :
gunzip: /root/uncom is a directory... (2 Replies)
Discussion started by: hoyanet
2 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)