10-16-2017
I am assuming the LD_LIBRARY_PATH works in AIX as it does elsewhere. Please correct me if this is a bad assumption. EDIT: checked - 5.1 AIX and earlier uses LIBPATH, which may be brought forward to other newer releases. Newer releases use LD_LIBRARY_PATH as I expected.
See if you can successfully run the ldd command as yourself against the compiled program. Try it again as root user.
It could be that LD_LIBRARY_PATH needs to change for your user. The differences in output of the two ldd commands should give you a clue.
As an aside, subverting/reinventing system calls like exit() is generally a poor idea. And it is sometimes done by using replacement shared libraries and/or changing the LD_LIBRARY_PATH order of shared libraries.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I'm receiving an exit code 64 in our batch scheduler (BMC product control-m) executing a PERL script on UX-HP. Can you tell me where I can find a list of exit codes and their meaning. I'm assuming the exit code is from the Unix operating system not PERL. (3 Replies)
Discussion started by: jkuchar747
3 Replies
2. Shell Programming and Scripting
I have a function that returns a bunch of exit codes, say func1, and in my code I'm trying to execute that function in an if statement. This is the closest I could get.
f1call=`func1 $arg1 $arg2`
if ]; then
...
fi
When I run the script the function never gets called. What's the right way... (7 Replies)
Discussion started by: eur0dad
7 Replies
3. Programming
What is the difference between using exit(0) and exit(1) to exit a program? Which should I use? (9 Replies)
Discussion started by: enuenu
9 Replies
4. UNIX for Dummies Questions & Answers
My job is launched using this command: I'm at home and having VPN drops so I used nohup and background.
nohup perf_mon -c rating_4_multi,cfg &
The main script is PID 26119, and the sub task under it is 26118 which is not running - just sits there. 26119 runs forever but nothing else runs. I... (2 Replies)
Discussion started by: ido1957
2 Replies
5. Shell Programming and Scripting
Hello Friends,
Hope you are doing well.
I just need a help in executing multiple processes.
I've written a shell script which calls another scritps. But the problem is there are too many processes to run, and each process takes about a min to finish its execution.
So, I want to just... (3 Replies)
Discussion started by: singh.chandan18
3 Replies
6. Shell Programming and Scripting
Hi
In one of the script I am seeing some thing like exit 7,exit 1,exit 2,exit 3,exit 9,exit6.What is the difference between all of this exit.Can anyone help here please (3 Replies)
Discussion started by: ginrkf
3 Replies
7. UNIX for Dummies Questions & Answers
Hi All,
I have one shell script start.sh which executes another shell script test.sh something like below :test.sh -param1 -param2
In the test.sh there is one command for removing file:rm file1.bak
I want whenever I execute start.sh, it will execute test.sh and if it finds string rm... (7 Replies)
Discussion started by: ORAI
7 Replies
8. Shell Programming and Scripting
Hi,
I am writing shell script to automate few use cases for CLI interface. We have CLI interface which has bunch of commands. I am trying to execute one of the commands 'exit' as part of automation to exit from CLI object (not from shell script) in my shell script.
My intension is to execute... (4 Replies)
Discussion started by: Mahesh Desai
4 Replies
9. Shell Programming and Scripting
i have a "if .. then exit end " in s shell script on remote servers.
now the connection to the remote server got killed after i run this script on the remote servers. How do i run this script on remote hosts and still keep remote connections alive after executing the script.
Thank you. (10 Replies)
Discussion started by: moonmonk
10 Replies
LEARN ABOUT DEBIAN
test::exit
Test::Exit(3pm) User Contributed Perl Documentation Test::Exit(3pm)
NAME
Test::Exit - Test that some code calls exit() without terminating testing
VERSION
version 0.03
SYNOPSIS
use Test::More tests => 4;
use Test::Exit;
exits_ok { exit 1; } "exiting exits"
never_exits_ok { print "Hi!"; } "not exiting doesn't exit"
exits_zero { exit 0; } "exited with success"
exits_nonzero { exit 42; } "exited with failure"
DESCRIPTION
Test::Exit provides some simple tools for testing that code does or does not call "exit()", while stopping code that does exit at the point
of the "exit()". Currently it does so by means of exceptions, so it will not function properly if the code under test calls "exit()"
inside of an "eval" block or string.
The only criterion tested is that the supplied code does or does not call "exit()". If the code throws an exception, the exception will be
propagated and you will have to call it yourself. "die()"ing is not exiting for the purpose of these tests.
exits_ok
Tests that the supplied code calls "exit()" at some point.
exits_nonzero
Tests that the supplied code calls "exit()" with a nonzero value.
exits_zero
Tests that the supplied code calls "exit()" with a zero (successful) value.
never_exits_ok
Tests that the supplied code completes without calling "exit()".
AUTHOR
Andrew Rodland <andrew@hbslabs.com>
COPYRIGHT AND LICENSE
This software is copyright (c) 2009 by HBS Labs, LLC..
This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.
perl v5.10.1 2009-12-04 Test::Exit(3pm)