I would test another binary that is compiled cobol...
The idea is MF from what I remember ( last time I had to touch and configure was 10 years ago...) has which seems to be your case (production) things that are run at boot time e.g. you would find in /etc a file, here on the last HP having it : mflmrcscript
with content:
SHLIB_PATH (HP) is your LD_LIBRARY_PATH (SUN)
As you can see, it is set up BEFORE $SHLIB_PATH for it has from what I remember some lib stuff having the same name as in $SHLIB_PATH and so it works because it takes the first it finds...
Now its difficult to compare with dev box because on dev boxes you have many compilers and libraries, so MF-Cobol dev suite is NOT the same and the order is less important because can be customized quite alot...
On production boxes you may just have the runtime (explaining why you have server express...)
One thing I know is if thoses MF daemon are not running, no cobol stuff will work... that is why my first line here
Vbe Thanks,
So what is the exact cause of my error and what can i do?
When i run bip.sh independently it works fine.So do i need to include some environmental variables in my script?
Last edited by rafa_fed2; 09-26-2013 at 07:06 AM..
Hi,
This question deals with Solaris 2.8 and setuid programs. From research I've done so far, setuid programs ignore LD_LIBRARY_PATH; I've proven this and am OK with it. The thing I am not certain of how the C compiler is supposed to behave when it is invoked via a setuid program. Basically,... (0 Replies)
Hello
I have just tried to install ns-allineone-2.31 on cygwin
cygwin is using the bash shell
it asks for somethings to be put into the LD_LIBRAY_PATH, here is a snippet of what it says.
(1) You MUST put /home/Chris/ns-allinone-2.31/otcl-1.13, /home/Chris/ns-allinone-2.31/lib, into your... (1 Reply)
I would like to know the differences between LIB_PATH and LD_LIBRARY_PATH on Linux and SunOS.
I am getting an error while loading shared libraries on Linux (Omni works build environment) as shown below:
1:tradewind/dataaccess/*.pcc... (1 Reply)
hi
Im using HP-UX 11i,PARISC .... Where do i find SHLIB_PATH or LD_LIBRARY_PATH ,
i couldnt find in env, listing...... Moreover im trying to execute file its throwing me error
usr/lib/dld.sl: Can't find path for shared library: libgcc_s.sl
/usr/lib/dld.sl: No such file or directory... (3 Replies)
Hi all!
I need to add new environment variable.
e.g. # setenv LD_LIBRARY_PATH "/usr/ucblib:"
#
I check:# env
LD_LIBRARY_PATH=/usr/ucblib:
After rebooting I don't see this variable.
Why don't save this variable?
Thanks. (5 Replies)
Inside my csh script, I have the following command:
source ${HOME}/.login
When I execute my csh script, why do I get the following error message:
/cygdrive/c/WINDOWS/system32/export: Permission denied
This is what I have inside my .login
#!/bin/bash
export... (9 Replies)
I have a question on setting environmental variable LD_LIBRARY_PATH.
The case is that, i cannot execute wget on my AIX machine.
It return the following error:
exec(): 0509-036 Cannot load program wget because of the following errors:
0509-022 Cannot load module... (5 Replies)
Hi.,
Currently my LD_LIBRARY_PATH setting is,
LD_LIBRARY_PATH=/opt/app/product/11.2.0/client_1/lib
Now, I need to append the JAVA to this setting...
Can I set this way, Please suggest.
... (4 Replies)
Hello, a few moments ago, I tried to compile lynx. It complained about the lack of ncurses. I downloaded it, compiled it and then installed it to non standard directory.
Going back to the lynx, I expected to pass ncurses location to it through a .pc file and PKG_CONFIG_PATH. However the version... (5 Replies)
Discussion started by: colt
5 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)