Automation script to reduce the installation time

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Need to reduce the execution time

We are trying to execute below script for finding out the occurrence of a particular word in a log file Need suggestions to optimize the script. Test.log size - Approx to 500 to 600 MB $wc -l Test.log 16609852 Test.log po_numbers - 11 to 12k po's to search $more po_numbers xxx1335...

2. Shell Programming and Scripting

Optimizing script to reduce execution time

AFILENAME=glow.sh FILENAME="/${AFILENAME}" WIDTHA=$(echo ${FILENAME} | wc -c) NTIME=0 RESULTS=$(for eachletter in $(echo ${FILENAME} | fold -w 1) do WIDTHTIMES=$(awk "BEGIN{printf...

3. Shell Programming and Scripting

Reduce the number of lines in script

Hello All, I have created a script which will show the errors from a log file in between a particular section. v1=$(sed -n "/Main Report/,/Main Report End/p" input | grep -i 'Unable to find' v2=$(sed -n "/Main Report/,/Main Report End/p" input | grep -i 'Unable to add' if then echo...

4. Shell Programming and Scripting

Script Automation

Hi Gurus, I have a clearcase script that i use to check in a single file at time on my clearcase server. the script is as follows setmyview settask 75098_MSI_TRILOGY_EIM cd /vobs/Trilogy_R12/custom/msieim/12.0.0/sql/ cleartool co -nc . ct mkelem -nc Filename_1.sql cp...

5. Shell Programming and Scripting

Help to reduce time of archiving

hi all, i have written the following script that does this work: 1. copy large logs files from one server to another. 2. then unzip this files and extraxt from these large https logs only those fields that are neccesary. 3. then archive the extracted logs to new files. BUT the problem is...

6. Shell Programming and Scripting

To reduce the bash script length!!!

Hi friends, at last i finish my script to find the status of the URL , in this code i used all the status codes, because of this it take too much of length. with the help of wiki only i find all the status codes. Status codes in HTTP #!/bin/bash timevar=`date +%d-%m-%Y_%H.%M.%S` #--...

7. Shell Programming and Scripting

need inputs on how i can change my script to reduce amount of time the script takes

HI , I have a list1 which consists of data that i have to search and a list2 which has the files that need to be searched .So basically i am using list1 on list2 to see if list1 data is present if found replace it .I have written the code using foreach loop for each list .This is taking the...

8. Shell Programming and Scripting

To reduce execution time

Hi All, The below script I run daily and it consumes 2 hours approx. In this I am calling another script and executing the same twice. Is the loop below the cause for the slow process?Is it possible to finetune the program so that it runs in a much faster way? The first script: #!/bin/ksh...

9. UNIX for Advanced & Expert Users

Last system installation time

Hi, What is the best way to find the last installation time of an unix based systems?Please advise Thanks Nagarajan G

10. BSD

Reduce boot-time delay on FreeBSD?

Say for instance, I would like to reduce the delay/waiting time for the boot-time menu from 10 seconds to 5 seconds, how would I go about doing it? From what I've been able to find, entering "autoboot 5" into the right file would take care of that for me, but the man pages are unclear as to...

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)

Shell Programming and Scripting