Issue with script in linux but in unix works

10 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

Expect scripting issue, works interactively when doing commands in cli, does not work in script

Hi; problem may be obvious, simple but I have to say it is somehow not easy to locate the issue. I am doing some word extracting from multiline text. Interacting in CLI seems to work without issues. First step is to add multiline text to a variable. expect1.1> expect1.1> set...

2. Shell Programming and Scripting

Why statement works in LINUX and not UNIX?

Hello, I have a ksh script that uses code below. For some reason it works under linux but fails in unix. Any idea why? if ]; then ... Thanks

3. Shell Programming and Scripting

Script works with Linux not with Solaris

Hi I have the following script which works in Linux shell but gives issues with Sun OS Solaris 5.10, What i am trying to achieve here is we have a list of file names in list.txt file and we parse each file at a time for a particular pattern and copt next 4 lines after we hit the pattern to a...

4. Shell Programming and Scripting

sed works on Linux and Unix does not work

Hi, I use this command in Linux but if I run the same command does not work in freebsd. Follow the below command: Linux works: sed -e '1731a\' -e '####' squid.conf > squid2.conf ; sed -e '1731a\' -e 'acl TESTE_ip src 192.168.1.1/255.255.255.255' squid2.conf > squid.conf ; sed -e...

5. UNIX for Dummies Questions & Answers

FTP that works correctly in command prompt and shows issue in UNIX server

Hi All, FTP ports opens with the given user name and password and allows to download file through COMMAND PROMPT. Code as below: H:\>ftp ftpxxxxx Connected to entvc2ft07-pub.xxxxx.com. 220 Microsoft FTP Service User (entvc2ft07-pub.xxxxx.com:(none)): userxxxxx 331 User name okay, need...

6. Shell Programming and Scripting

Works in shell but not script UNIX

ok i have a very simple UNIX script #!/bin/bash TERM=ansi;export TERM PFCMARK=25;export PFCMARK umask 0000 PFUMASK=000;export PFUMASK #run for filepro menus and exectuables echo "###########File Modification Log.############\r" > "/public/appl-fp$(date +%m-%d-%Y).txt" find /appl/fp/...

7. Shell Programming and Scripting

Execution issue with shell script - works in a different environment

Hi I get the following error while executing the shell script. I did not get an error when I ran the script in a different environment (unix server). str-token.ksh: 0403-057 Syntax error at line 20 : `(' is not expected. This is the line which gives error string=(${pos_array}) Please find...

8. UNIX for Dummies Questions & Answers

what's the Linux|Unix OSes works on Servers

Hi everybody , I'm new here in the forum and new Dummy in L|U systems (Hope finding welcomes...:)). I just want to ask : What is the OS's that works on servers and the OS's that work as client OS?? I just know that Solaris Work on sarvers :D.. and i'm glad to be memmber in this...

9. Shell Programming and Scripting

Script works on Solaris, not on Linux

I'm in the same boat as Barbus - same exercis (https://www.unix.com/shell-programming-scripting/43609-processes-users.html) The following script works on a solaris server I have access to. It doesn't however, work on the companies Linux machine. Any idea what's up? I have very little shell...

10. Shell Programming and Scripting

Script works on Solaris, not on Linux

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)

Shell Programming and Scripting