(No, this is just another way to run it on SPARC serverB.)
Check with
where the shared libraries are located.
You need to tweak LD_LIBRARY_PATH before you can run the /export/home/user2/utils/plugin/Test.exe.
Maybe you do this in your ~/.profile or ~/.bashrc_profile?
I'm sorry as i could not understand the solution proposed.
If you look at the error it says
Quote:
fatal: libFPCore32.so: open failed: No such file or directory
"libFPCore32.so" is present on serverB(solaris) @ /opt/product/bin/libFPCore32.so
Can't find "libFPCore32.so" on ServerA(linux). I m also not sure where where the shared Libraries are location on ServerB
on ServerB the shared Libraries are here:
I guess you are asking me to make these changes.
1. Change runme.sh on serverB from /export/home/user2/utils/plugin/Test.exe to ldd /export/home/user2/utils/plugin/Test.exe
2. on ServerA modify the .profile and add the correct export LD_LIBRARY_PATH
(Note: I m however not sure where the LD_LIBRARY_PATH [shared library path] is )
Please let me know if there anything more i need to do apart from the above 2 points?
Hi guys,
I Have written a script,In that it will call another file which contains the sql quaries.
while wxecuting that I am getting the below exception
01/16|06:28:06:16800: Operating System Error|Failed to open output file
Can anybody help me about this,,Its urgent (0 Replies)
I'm on ubuntu fiesty using svn as version control and gvim as my IDE.
i like to review changes to files before checking them in. at some point in my life i used
" svn diff {path}/{filename} "
this now returns
Index: {path}/{file}... (5 Replies)
Hi,
I am working with solaris 9 and I want to install perforce on that,so I downloaded the p4v.bin file and try to install it by the command
./p4v
after that it is giving the error---
ld.so.1: ./p4v.bin: fatal: libm.so.2: open failed: No such file or directory
Killed
I am not... (3 Replies)
Hi Friends
I have a compiler(Sun Forte,I believe) running in my Solaris 9 box.
since y'day my development team is finding this error when they compile:
ld.so.1: expr: fatal: libgmp.so.3: open failed: No such file or directory
I ran a search for this file and found it in one of my file... (2 Replies)
Hi,
I have try to ndm to one server to another server. but i am getting this error. what is this error? are files not in source folder?
Source file open failed. Error= 2
Regards,
Balamurgan (1 Reply)
I am seeking help on one script that I created to celan up database audit files. The error returned is
$./clean_audit.sh: /opt/oracle/logs/audit_clean.log: cannot open The same script is working on other 2 or 3 servers. But not working on other 4 servers. All servers are Oracle Linux. Here is... (21 Replies)
Hi Guys,
I am facing this Error
bash-2.03$ ./curl -V
ld.so.1: curl: fatal: libldap.so.5: open failed: No such file or directory
Killed
bash-2.03$
while executing
./curl -V in /opt/sfw/bin directory.
I am using Sun Solaris 10.
which package upgrage can give me this missing... (9 Replies)
I just updated my rdesktop to 1.8.3 from source ( on Slackware 11 ) and had troubles with arrow keys/page up/page down not working.
I see this on the console:
ERROR: Failed to open keymap en-us
The fix is a permission change. I initially looked at /usr/share/rdesktop/keymaps and everything... (1 Reply)
I wish to copy all the files & folder under /web/Transfer_Files/data/ on mymac1 (Linux) to remote server mybank.intra.com (Solaris 10) /tmp/ location
I am using Ansible tool synchronize module which triggers the unix rsync command as below:rsync --delay-updates -F --compress --archive --rsh=ssh... (2 Replies)
Hello all,
I have a task to patch red hat servers and some servers have a corrupted rpm database and return the error:
Error: rpmdb open failed
I know how to fix this when it occurs. What I'm hoping to do is scan a list of servers by IP and report back which server have this error.
... (6 Replies)
Discussion started by: greavette
6 Replies
LEARN ABOUT X11R4
environment.d
ENVIRONMENT.D(5) environment.d ENVIRONMENT.D(5)NAME
environment.d - Definition of user session environment
SYNOPSIS
~/.config/environment.d/*.conf
/etc/environment.d/*.conf
/run/environment.d/*.conf
/usr/lib/environment.d/*.conf
/etc/environment
DESCRIPTION
The environment.d directories contain a list of "global" environment variable assignments for the user environment. systemd-environment-d-
generator(8) parses them and updates the environment exported by the systemd user instance to the services it starts.
It is recommended to use numerical prefixes for file names to simplify ordering.
For backwards compatibility, a symlink to /etc/environment is installed, so this file is also parsed.
CONFIGURATION DIRECTORIES AND PRECEDENCE
Configuration files are read from directories in /etc/, /run/, and /lib/, in order of precedence. Each configuration file in these
configuration directories shall be named in the style of filename.conf. Files in /etc/ override files with the same name in /run/ and
/lib/. Files in /run/ override files with the same name in /lib/.
Packages should install their configuration files in /lib/. Files in /etc/ are reserved for the local administrator, who may use this logic
to override the configuration files installed by vendor packages. All configuration files are sorted by their filename in lexicographic
order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with the
lexicographically latest name will take precedence. It is recommended to prefix all filenames with a two-digit number and a dash, to
simplify the ordering of the files.
If the administrator wants to disable a configuration file supplied by the vendor, the recommended way is to place a symlink to /dev/null
in the configuration directory in /etc/, with the same filename as the vendor configuration file. If the vendor configuration file is
included in the initrd image, the image has to be regenerated.
CONFIGURATION FORMAT
The configuration files contain a list of "KEY=VALUE" environment variable assignments, separated by newlines. The right hand side of these
assignments may reference previously defined environment variables, using the "${OTHER_KEY}" and "$OTHER_KEY" format. It is also possible
to use "${FOO:-DEFAULT_VALUE}" to expand in the same way as "${FOO}" unless the expansion would be empty, in which case it expands to
DEFAULT_VALUE, and use "${FOO:+ALTERNATE_VALUE}" to expand to ALTERNATE_VALUE as long as "${FOO}" would have expanded to a non-empty value.
No other elements of shell syntax are supported.
Each KEY must be a valid variable name. Empty lines and lines beginning with the comment character "#" are ignored.
Example
Example 1. Setup environment to allow access to a program installed in /opt/foo
/etc/environment.d/60-foo.conf:
FOO_DEBUG=force-software-gl,log-verbose
PATH=/opt/foo/bin:$PATH
LD_LIBRARY_PATH=/opt/foo/lib${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}
XDG_DATA_DIRS=/opt/foo/share:${XDG_DATA_DIRS:-/usr/local/share/:/usr/share/}
SEE ALSO systemd(1), systemd-environment-d-generator(8), systemd.environment-generator(7)systemd 237ENVIRONMENT.D(5)