09-06-2011
I guess sudo does not preserve your $LD_LIBRARY_PATH with :/usr/local/lib:
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi All,
We have a gtar file and we are trying to untar the file with the option
gtar -xvzf <filename>
The gtar gets us till the end and throws the error message as highlighed below
mfcp/XFHFCD2.CPY
mfcp/XFHFCD3.CPY
mfcp/XFHFCD.CPY
gzip: stdin: unexpected end of file
gtar:... (1 Reply)
Discussion started by: ganga.dharan
1 Replies
2. UNIX for Dummies Questions & Answers
I am trying to write a very large file, 570 gb, to a tape using gtar like this :
gtar czxf /dev/rmt/1 ./*
I get a message:
off_t value 570635451556 too large (max=68719476735)
It is writing to tape, but will it be good?
Thanks (1 Reply)
Discussion started by: iancrozier
1 Replies
3. Solaris
Hi all,
will gtar zcvf command work in csh and tcsh shells? Becuase when i'm executing one script in bash and ksh, it's working fine. But it's not working in csh and tcsh shells. We have to run multiple scripts in tcsh, so we can not change the shell while executing these scripts. One of my... (2 Replies)
Discussion started by: raghu.iv85
2 Replies
4. Solaris
deleteing post (0 Replies)
Discussion started by: dshakey
0 Replies
5. Red Hat
Hello,
I'm experimenting a problem on my rh server.
Red Hat Enterprise Linux AS release 3 (Taroon Update 8)
2.4.21-47.ELsmp #1 SMP i686 i686 i386 GNU/Linux
It started with a segmentation fault on
#id root
To resolve it, I've installed
coreutils-4.5.3-28.4.i386.rpm
But, I... (6 Replies)
Discussion started by: gogol_bordello
6 Replies
6. Red Hat
# service httpd start
Starting httpd: Syntax error on line 6 of /etc/httpd/conf.d/php.conf:
Cannot load /etc/httpd/modules/libphp4.so into server: /lib/tls/libc.so.6: version `GLIBC_2.4' not found (required by /lib/libgcc_s.so.1)
I... (2 Replies)
Discussion started by: getrue
2 Replies
7. Shell Programming and Scripting
I have a C++ binary executable installed in a file system which is shared across multiple solaris boxes.
When I start this executable from one of the boxes,I am able to start only 4 parallel instances and from the 5th instance onwards I am getting the following error.
fatal: libdb2.so.1:... (2 Replies)
Discussion started by: prasperl
2 Replies
8. AIX
We are taking backup of our application data(cobol file system, AIX/unix) before and after EOD job runs. The data size is approximately 260 GB in biggest branch. To reduce the backup time, 5 parallel execution is scheduled through control-m which backups up the files in 5 different *.gz. The job... (2 Replies)
Discussion started by: Bharath_79
2 Replies
9. AIX
We are taking backup of our application data(cobol file system, AIX/unix) before and after EOD job runs. The data size is approximately 260 GB in biggest branch. To reduce the backup time, 5 parallel execution is scheduled through control-m which backups up the files in 5 different *.gz. The job... (8 Replies)
Discussion started by: Bharath_79
8 Replies
10. Red Hat
Hello,
I am trying to run a chess pairing program called Vega Chess on RHEL 6.5 Server
$ uname -a
Linux CDMA 2.6.32-431.el6.i686 #1 SMP Sun Nov 10 22:20:22 EST 2013 i686 i686 i386 GNU/Linux
$ cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.5 (Santiago)This is the way I... (6 Replies)
Discussion started by: Ferocci
6 Replies
LEARN ABOUT XFREE86
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 237 ENVIRONMENT.D(5)