01-23-2012
Shared File system- lib access issue
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: open failed
I am able to start only 4 processes from a shell.If I exist from current shell and start another 4 from new shell,it is working fine.
Is this something due to shared FS?
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
We build our code on all platforms Sol, Hp, Aix, Sgi & linux.
Some base libraries have changed.
All the dependent exe & lib which use those base libraries have changed in all platforms in terms of size/checksum or both except linux.
No code has changed in these.
We have a post utility... (8 Replies)
Discussion started by: vibhor_agarwali
8 Replies
2. HP-UX
im not good with this stuff but the app guys game to me with a problem with there c++ program on a new box, any ideas?
bin- ./qeng
Bus error (core dumped)
bin- ./gdb qeng core
Wildebeest is free software and you are welcome to distribute copies of
it under certain conditions; type "show... (4 Replies)
Discussion started by: csaunders
4 Replies
3. UNIX for Dummies Questions & Answers
Hello ALL,
In my system, there are 14 machines running the same version of Linux RHEL4. The 14 machines use a NFS file system, i.e., a shared file system.
My question is that if the programs in individual machines can access a common file simutaneously. Or, they have to access the file... (1 Reply)
Discussion started by: cy163
1 Replies
4. UNIX for Dummies Questions & Answers
I was curious how to tell which programs are accessing a file (libobjc.A.dylib) in /usr/lib
This file seems to be the culprit in a bunch of Safari crashes, and I just wanted to know if and what other programs use it.
Also, I was curious what a good way to find out what files are being written... (4 Replies)
Discussion started by: glev2005
4 Replies
5. AIX
Hi,
I want to change the values for shared file system in aix for that I have run the command smitty chnfsexp but I am not getting the all the values which I have seen while adding the file system while exporting
example
smitty chnfsexp
but after selecting shared file system using F4... (3 Replies)
Discussion started by: manoj.solaris
3 Replies
6. UNIX for Advanced & Expert Users
Hi Everybody..
I am using Moblin V2 which has nautilus file manager the one which is also used in Ubuntu.
I want to lock the access to file system such that i can only browse my home folder not other locations like /, /usr, /bin and all.
Or i want to create a partition of 10 or 15 GB so... (1 Reply)
Discussion started by: lokeshsingla
1 Replies
7. Programming
for example, I have a static lib name liba.a
it offers some interface such a1();a2();
but i do not have the source code of liba.a;
If i would like to create a shared object, and offer the similar interface of
a1 and a2;
Is there a way to fulfill such requirement?
thanks. (7 Replies)
Discussion started by: flost
7 Replies
8. Solaris
Hi All,
I have configured the tomcat 6.0.26 and it is working fine in Solaris.
Testing JSP and SERVLET program I ensured tomcat is configured properly (My guess).
-------------------
Now I placed my Servlet and JSP code under /users/kalai/sample.
I have created a soft link to... (1 Reply)
Discussion started by: kalpeer
1 Replies
9. UNIX for Advanced & Expert Users
I would be taking my masters degree project next year. So I am now in the process of thinking something that could help me get more in depth knowledge and will be a useful one in practice.
I have thought about creating shared file system for clustered environments (like GPFS,GFS).
I have... (4 Replies)
Discussion started by: kumaran_5555
4 Replies
10. Red Hat
Hi, I am facing a weird file access time issue on redHat5.x. I have a program which will scan the files in the NFS system and delete files which are older than 4 days, before deleting files program will print the access time of the file.
Some of the files are getting deleted which are not older... (1 Reply)
Discussion started by: Satyak
1 Replies
LEARN ABOUT PLAN9
dh_installsystemd
DH_INSTALLSYSTEMD(1) Debhelper DH_INSTALLSYSTEMD(1)
NAME
dh_installsystemd - install systemd unit files
SYNOPSIS
dh_installsystemd [debhelperoptions] [--restart-after-upgrade] [--no-stop-on-upgrade] [--no-enable] [--name=name] [unitfile...]
DESCRIPTION
dh_installsystemd is a debhelper program that is responsible for enabling, disabling, starting, stopping and restarting 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.
For only generating blocks for specific service files, you need to pass them as arguments, e.g. dh_installsystemd quota.service and
dh_installsystemd --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. Please remember to also use --no-start if the service should
not be started.
--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_installsystemd looks for and installs files named debian/package.name.service instead of the usual debian/package.service.
Moreover, maintainer scripts are only generated for units that match the given name.
--restart-after-upgrade
Do not stop the unit file until after the package upgrade has been completed. This is the default behaviour in compat 10.
In earlier compat levels the default was to stop the unit file in the prerm, and start it again in the postinst.
This can be useful for daemons that should not have a possibly long downtime during upgrade. But you should make sure that the daemon
will not get confused by the package being upgraded while it's running before using this option.
--no-restart-after-upgrade
Undo a previous --restart-after-upgrade (or the default of compat 10). If no other options are given, this will cause the service to
be stopped in the prerm script and started again in the postinst script.
-r, --no-stop-on-upgrade, --no-restart-on-upgrade
Do not stop service on upgrade.
--no-start
Do not start the unit file after upgrades and after initial installation (the latter is only relevant for services without a
corresponding init script).
Note that this option does not affect whether the services are enabled. Please remember to also use --no-enable if the services should
not be enabled.
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.
SEE ALSO
debhelper(7)
AUTHORS
pkg-systemd-maintainers@lists.alioth.debian.org
11.1.6ubuntu2 2018-05-10 DH_INSTALLSYSTEMD(1)