03-26-2008
Quote:
Originally Posted by
System Shock
You don't need patches. You need to either a) install the C libraries package -sunfreeware.com has a package that you can install with pkgadd; or b) the library may be installed, but not in your path.
This is what I would do. Afterwards don't forget to update using crle -u -l /opt/sfw/lib.
after that you should be able to run whatever it is you need to run.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
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)
Discussion started by: Anji
0 Replies
2. Solaris
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)
Discussion started by: smartgupta
3 Replies
3. Solaris
Hi all,
when am rebooting the server (SF v890) we are facing
"open boot diagnostic failed".
Thanks in Adv. (5 Replies)
Discussion started by: arjunreddy3
5 Replies
4. Solaris
Hi all.
I try to start an application, but libucb.so1 is missing.
# appl23
# appl23ld.so.1: appl23: fatal: libucb.so1: open failed: No such file or directory
killed
#
# ldd appl23
libXm.so.3 => /usr/lib/libXm.so.3
libMrm.so.3 => /usr/lib/libMrm.so.3
... (14 Replies)
Discussion started by: wolfgang
14 Replies
5. Programming
Hello,
I want to migrate from application that was compiled with Sun 4.2 compiler with C++ standard library(libCstd.so.1) to STLport(libstlport.so.1) library.
I am able to compile all the files on Solaris 10 with Sun 5.8 compiler but linking is failing with symbol referencing errors though... (0 Replies)
Discussion started by: shafi2all
0 Replies
6. UNIX for Dummies Questions & Answers
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)
Discussion started by: krbala1985
1 Replies
7. Red Hat
Hi,
# yum --skip-broken -y update
rpmdb: Thread/process 6657/3078387392 failed: Thread died in Berkeley DB library
error: db3 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Packages index using db3 - (-30974)
error: cannot open... (3 Replies)
Discussion started by: sef alislam
3 Replies
8. Solaris
Hey for some reason I think I deleted a critical file for sendmail. I was looking the log file on /var/log/cron for cron, and the file isn't there and I found out the reason why is because I'm missing libssl.so.0.9.7. Im running Solaris 11.
I checked smtp and got the following:
#svcs -xv... (3 Replies)
Discussion started by: picolin
3 Replies
9. UNIX for Beginners Questions & Answers
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)
Discussion started by: agentrnge
1 Replies
10. Shell Programming and Scripting
Hi, The below commands works fine on serverB
. /etc/profile;
cd /export/home/user2/utils/plugin/
./runme.shHowever, when i run the same commands from serverA it fails
$ ssh -q user2@serverB ". /etc/profile; cd /export/home/user2/utils/plugin; ./runme.sh"Output Error:
Please find the below... (8 Replies)
Discussion started by: mohtashims
8 Replies
LEARN ABOUT PLAN9
dh_systemd_enable
DH_SYSTEMD_ENABLE(1) Debhelper DH_SYSTEMD_ENABLE(1)
NAME
dh_systemd_enable - enable/disable systemd unit files
SYNOPSIS
dh_systemd_enable [debhelperoptions] [--no-enable] [--name=name] [unitfile...]
DESCRIPTION
dh_systemd_enable is a debhelper program that is responsible for enabling and disabling systemd unit files.
In the simple case, it finds all unit files installed by a package (e.g. bacula-fd.service) and enables them. It is not necessary that the
machine actually runs systemd during package installation time, enabling happens on all machines in order to be able to switch from
sysvinit to systemd and back.
In the complex case, you can call dh_systemd_enable and dh_systemd_start manually (by overwriting the debian/rules targets) and specify
flags per unit file. An example is colord, which ships colord.service, a dbus-activated service without an [Install] section. This service
file cannot be enabled or disabled (a state called "static" by systemd) because it has no [Install] section. Therefore, running
dh_systemd_enable does not make sense.
For only generating blocks for specific service files, you need to pass them as arguments, e.g. dh_systemd_enable quota.service and
dh_systemd_enable --name=quotarpc quotarpc.service.
FILES
debian/package.service, debian/package@.service
If this exists, it is installed into lib/systemd/system/package.service (or lib/systemd/system/package@.service) in the package build
directory.
debian/package.tmpfile
If this exists, it is installed into usr/lib/tmpfiles.d/package.conf in the package build directory. (The tmpfiles.d mechanism is
currently only used by systemd.)
debian/package.target, debian/package@.target
If this exists, it is installed into lib/systemd/system/package.target (or lib/systemd/system/package@.target) in the package build
directory.
debian/package.socket, debian/package@.socket
If this exists, it is installed into lib/systemd/system/package.socket (or lib/systemd/system/package@.socket) in the package build
directory.
debian/package.mount
If this exists, it is installed into lib/systemd/system/package.mount in the package build directory.
debian/package.path, debian/package@.path
If this exists, it is installed into lib/systemd/system/package.path (or lib/systemd/system/package@.path) in the package build
directory.
debian/package.timer, debian/package@.timer
If this exists, it is installed into lib/systemd/system/package.timer (or lib/systemd/system/package@.timer) in the package build
directory.
OPTIONS
--no-enable
Disable the service(s) on purge, but do not enable them on install.
Note that this option does not affect whether the services are started. That is controlled by dh_systemd_start(1) (using e.g. its
--no-start option).
--name=name
Install the service file as name.service instead of the default filename, which is the package.service. When this parameter is used,
dh_systemd_enable looks for and installs files named debian/package.name.service instead of the usual debian/package.service.
NOTES
Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command (with the same arguments).
Otherwise, it may cause multiple instances of the same text to be added to maintainer scripts.
Note that dh_systemd_enable should be run before dh_installinit. The default sequence in dh does the right thing, this note is only
relevant when you are calling dh_systemd_enable manually.
SEE ALSO
dh_systemd_start(1), debhelper(7)
AUTHORS
pkg-systemd-maintainers@lists.alioth.debian.org
11.1.6ubuntu2 2018-05-10 DH_SYSTEMD_ENABLE(1)